<!-- m --><a class="postlink" href="http://www.penguinz.net/members.php">http://www.penguinz.net/members.php</a><!-- m -->
It always baffles me when the code works fine in IE, but Firefox totally misinterprets it. Are there any sites (or people) who could point me to some hints what I'm doing wrong?
Thanks,
MatthewIn all liklihood, the code is incorrect and Firefox is displaying 'correctly' (showing you errors and misaligned stuff), while IE more-or-less understands 'broken code', and shows you what you want to see. One only need visit an 'best viewed in IE' page using Firefox (or Mozilla or Opera for that matter, among others...) and see the page fall apart and reach the same conclusion, -that IE does thing 'wrong'. Hmmph.
Anyway, I'll look it over and see if anything jumps out at me but surely others here will come to your aid as well.
The users of this Forum are top-notch.I shouldn't have said "misinterprets" -- what I should have said was "seeminly misinterprets seemingly good code".
I know there are several rendering errata, many of which have names. I am completely new to programming cross-browser, and it seems quite overwhelming at first. I need a few important starters, maybe using my page as an example of one of the bugs.
Then I'll never do it again!
Thanks,
MatthewYou are using a few "position:absolute" statements in conjunction with z-index: statements... -wasn't there something about z-indexes not working dependably in 'absolute' positioning of DIV (or other 'containers')? I recall reading about that somewhere, that position:relative is used (specifically) to 'gain control over the z-index' statement. -Anyone? Am I waaaay off base here and not addressing the issue?
Myself, I will admit that I run into problems whenever I start using 'absolute' positioning more than once (or twice) in any one web creation (owing partly to my youth and inexperience with the statement's proper use, I am sure...)
Next?
-JoelThe very first thing is to get all browsers on the same page of rules. This is done using a doctype. See my link below. IE is in 'quirks' mode and you will never know what the heck it will do.
Always design your site using Firefox or Opera or Safari. Then your code will be good and it will work in all browsers except, perhaps, IE. You hopefully will only have to make adjustments for IEs quirks and bugs.Always validate your code. You have a couple of html errors and a bazillion CSS errors. The CSS errors mainly relate to unspecified units, ie, you need to specify px, ems, percent or whatever and not just insert numbers.<!-- m --><a class="postlink" href="http://validator.w3.org/check?verbose=1&uri=http://www.penguinz.net/members.php">http://validator.w3.org/check?verbose=1 ... embers.php</a><!-- m -->
<!-- m --><a class="postlink" href="http://jigsaw.w3.org/css-validator/validator?profile=css2&warning=2&uri=http://www.penguinz.net/members.php">http://jigsaw.w3.org/css-validator/vali ... embers.php</a><!-- m -->
It always baffles me when the code works fine in IE, but Firefox totally misinterprets it. Are there any sites (or people) who could point me to some hints what I'm doing wrong?
Thanks,
MatthewIn all liklihood, the code is incorrect and Firefox is displaying 'correctly' (showing you errors and misaligned stuff), while IE more-or-less understands 'broken code', and shows you what you want to see. One only need visit an 'best viewed in IE' page using Firefox (or Mozilla or Opera for that matter, among others...) and see the page fall apart and reach the same conclusion, -that IE does thing 'wrong'. Hmmph.
Anyway, I'll look it over and see if anything jumps out at me but surely others here will come to your aid as well.
The users of this Forum are top-notch.I shouldn't have said "misinterprets" -- what I should have said was "seeminly misinterprets seemingly good code". I know there are several rendering errata, many of which have names. I am completely new to programming cross-browser, and it seems quite overwhelming at first. I need a few important starters, maybe using my page as an example of one of the bugs.
Then I'll never do it again!
Thanks,
MatthewYou are using a few "position:absolute" statements in conjunction with z-index: statements... -wasn't there something about z-indexes not working dependably in 'absolute' positioning of DIV (or other 'containers')? I recall reading about that somewhere, that position:relative is used (specifically) to 'gain control over the z-index' statement. -Anyone? Am I waaaay off base here and not addressing the issue?
Myself, I will admit that I run into problems whenever I start using 'absolute' positioning more than once (or twice) in any one web creation (owing partly to my youth and inexperience with the statement's proper use, I am sure...)
Next?
-JoelThe very first thing is to get all browsers on the same page of rules. This is done using a doctype. See my link below. IE is in 'quirks' mode and you will never know what the heck it will do.
Always design your site using Firefox or Opera or Safari. Then your code will be good and it will work in all browsers except, perhaps, IE. You hopefully will only have to make adjustments for IEs quirks and bugs.Always validate your code. You have a couple of html errors and a bazillion CSS errors. The CSS errors mainly relate to unspecified units, ie, you need to specify px, ems, percent or whatever and not just insert numbers.<!-- m --><a class="postlink" href="http://validator.w3.org/check?verbose=1&uri=http://www.penguinz.net/members.php">http://validator.w3.org/check?verbose=1 ... embers.php</a><!-- m -->
<!-- m --><a class="postlink" href="http://jigsaw.w3.org/css-validator/validator?profile=css2&warning=2&uri=http://www.penguinz.net/members.php">http://jigsaw.w3.org/css-validator/vali ... embers.php</a><!-- m -->