Jump to content
xisto Community

Tyssen

Members
  • Content Count

    1,159
  • Joined

  • Last visited

Everything posted by Tyssen

  1. It might also help if you specify which forum you're using. Also, the line number errors in PHP don't always point at the line that's causing the problem. It could be that something's missing from the one of the preceding lines (like a closing ; or } ) but the error is generated on the line that it doesn't expect to be there.
  2. I'm not aware of any way that you can access information from your database without the form being submitted to the server, so in other words, you're not going to get any 'real time' interaction as the person is typing. Remember, that only javascript can be used for client-side interaction which is what you're talking about here. Everything else has to be submitted to the server first.You might be able to access your db and get it to print out an array of suitable words into a javascript function which is then tied to your text inputs, but it seems like it'd be a lot of work for a fairly small return.The other possibility is that you might be able to accomplish what you want with AJAX but I don't know enough about it.
  3. I'm not positive, but I think he may have been talking about CSS hacks to feed certain rules to some browsers and not others, e.g.: * html #yourDiv {width: 200px;w\idth: 220px;}That gives one value to IE5+ but then sets it back again for IEMac/IE6. The rule is ignored by all other browsers. There are other selectors you can use to feed rules to non-IE browsers only too.
  4. Have you got padding applied to any of the elements involved? And rather than setting margin:0 the way you have, you'd be better off doing this: * { margin: 0; }That sets it to 0 for every element. Then you put it back on for the ones you want it to have.
  5. Tyssen

    Text Problem

    You can't have <html> & <body> tags inside a table cell.
  6. That's more than likely cos the designers have built & tested their sites in IE only which gets the W3C specs wrong in so many ways. It's not FF rendering poorly; it's developers designing poorly. And little wonder that the incidence is likely to be high amongst Xisto members.
  7. You may not need your home PC to be a server, but if you do a lot of web design/development work, it's invaluable to be able to test your pages in a real server environment locally - saves you having to upload stuff constantly to check changes you're making. (Then again, this is only really useful if you're working in ASP which I am a lot of the time.)
  8. In this case you are, because that's not the end result.
  9. Are you using absolute positioning for everything?
  10. You can't use position:absolute and float: right together. position:absolute overrides the float. You should be wary of using absolute positioning at all. You should be using float: right but due to too much stuff being positioned absolutely, you're running into troubles. Lose all the absolute positioning, use the normal flow of the document instead and use floats when you want stuff to be left or right.
  11. Link's not working. Any time something looks right in IE but not FF, you know there's something wrong with your code cos IE doesn't follow the W3C specs properly in a lot of cases.
  12. Rather than guessing as to what your page looks like and what might be a solution, why not post a link to the page or at least the code involved so that people have a better chance of suggesting something useful?
  13. The specs say that elements that are floated or positioned absolutely are taken out of the normal flow of the document. The specs also say that containers shouldn't expand to contain these out-of-flow elements. FF adheres to this spec; IE doesn't and expands to contain these elements. I'm not quite sure how overflow:hidden works in respect to solving the issue in browsers that follow the spec, but it does. It's all a question of relative to what. The thing is, using the normal flow of the document and using elements' margins/borders etc., you can position elements where you want them without ever having to resort to position: relative or position: absolute. As I said in that article on the other site, using position: something creates a new positioning context for elements. The only time I ever use position: relative is when I want an element contained within that element to be positioned absolutely relative to the containing element rather than the body. Or, if I want to give a z-index to something because z-index only works on elements that have position: something applied to it. So, in a lot of cases when I use it, applying position: relative to something doesn't actually affect that element's position, but rather affects the way elements contained within it behave.
  14. Add overflow:hidden to div.body to sort out your problem for FF. I really would recommend losing the absolute positioning though. Absolute positioning is something that should be avoided until you really understand the Visual Formatting Model.
  15. I dunno what you're going off about. I read the previous quote as being: most people who don't upgrade don't do so because they don't know how, ie, not very technical-minded. So the point is those people won't appreciate the extra effort gone into making a site as standards-compliant, and cross browser compatible as possible because they don't understand any of that stuff anyway.
  16. Without addressing your problem directly, here's a couple of tips: 1. Don't develop your sites in IE; use FF instead and then institute workarounds for IE's incorrect adherence to certain CSS specs. 2. Don't use absolute positioning. Here's an article on reasons why not.
  17. Is the Armenian tourist board paying commissions to people or something cos we had a very similiar thread to this not so long ago. Quick question for ya, do all Armenian surnames end in ...ian?
  18. Dropdowns will behave just like folders in Windows Explorer - type in some letters and it'll take you to it. Text inputs would be an entirely different story. You might be able to do it using javascript but I can see it being difficult to code especially when you have to consider that each browser is already going to have its own store of words previously typed into form elements which might clash with what the javascript is trying to output.
  19. I'm sorry, what's the actual question?
  20. There's a lot more to it than that. Domain name, page title, meta tags, page content, keyword density in all of those and how your pages are actually structured all play a part in how your site is indexed.
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.