Rank: ? (3)
Member #: 25408

Hi folks,

I've been working hard on extending the example login script and have been working on a simple menu system using DIV but I was testing my code in IE and not Mozilla as I read that DIV support is better in IE than Mozilla as Mozilla would normally use Layers.

Anyway I've got some generated code from a php script and I've tested the same code in IE and Mozilla and it seems not to work in IE but its fine in Mozilla

Code:


Can any of you folks tell me what is wrong from an IE point of view.

Thanks in advance
Carl

Rank: ? (4821)
Member #: 3416

i'm not sure where you read that, but it's completely wrong. both browsers do perfectly fine with div tags, though ie has some issues with applying css.

the problem you're having though is probably due to your html having problems: you didn't close the table tag. i inserted </table> before the closing div tag from #menu and everything displayed the same in firefox and ie, though it caused #home to overlap #menu since it's no longer contained within #menu...

Rank: ? (779)
Member #: 14565

IE has problems with everything. It's a pain especially for positioning DIVs in Firefox vs. IE...

Rank: ? (90)
Member #: 1672

IE is more of a nazi when it comes to error checking CSS code. Just like the W3C validator.

However I find Firefox more frustrating to work with then IE.

Rank: ? (779)
Member #: 14565

Then you are wierd, stu.

DO NOT STANDARDIZE YOUR WEBSITES TO IE! IE IS NOT A MODERN WEB BROWSER ANYMORE!

FORCE PEOPLE TO USE ALTERNATIVE BROWSERS!

Rank: ? (4821)
Member #: 3416

do you mean because there's a lot of css that ie doesn't support, or something else? generally ie is very lax in what it accepts (good for users, bad for developers). i would say that mozilla is the strict one since one of its goals has been to promote standards where ie is mostly concerned with being the most popular browser. if you want to make a site that works okay in all current browsers, the generally-agreed easiest is to code to standards and test first in a gecko-based browser, then check in ie and any other engines you care about and tweak things from there. of course it's always easiest to just pick one browser and only develop for that, but it's far from the best way.


by locking them out of the most common alternative? that's not the best way to convince people. i simply have a list of things that each browser doesn't support (or has a bug with) so people can read about what they're missing.