Internet Exploiter
Nov. 21st, 2003 02:20 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
elfsI hate Internet Explorer.
One of the requirements where I work is that the next major rev of the product be "Section 508 Compatible." What this means shorthand is that the pages rendered by the user iinterfact must scale well when fonts are altered, and must not contain clutter that would detract from the useability of the site when rendered by a text-to-voice system.
One of the things that makes 508 compliance easy is cascading style sheets, which (in theory) allow you to make the page pretty without detracting from the overall structural composition of the information. This would be nice, if it were true.
But IE doesn't make it nice. A simple example: the CSS2 standard states that the "hover" attribute applies to any block-level element. The example provided by the CSS2 standards team shows the usual "links turn different colors when you hover the mouse over them" effects. Mozilla correctly allows hover to work for any block-level element. IE only allows it to work for links. Mozilla correctly resizes containing elements if the hover defines a different type style. IE doesn't.
Another example is margins. The margin is the whitespace inside the border of an object, between its content and the border. (Padding is outside the border. The "border" is not necessarily a visible object.) Mozilla correctly spaces objects that use this attribute; IE does not. It's frustrating to read the freaking standard only to learn that the most common browser in the world often ignores what it says.
Why the Hell does anyone still use IE?
One of the requirements where I work is that the next major rev of the product be "Section 508 Compatible." What this means shorthand is that the pages rendered by the user iinterfact must scale well when fonts are altered, and must not contain clutter that would detract from the useability of the site when rendered by a text-to-voice system.
One of the things that makes 508 compliance easy is cascading style sheets, which (in theory) allow you to make the page pretty without detracting from the overall structural composition of the information. This would be nice, if it were true.
But IE doesn't make it nice. A simple example: the CSS2 standard states that the "hover" attribute applies to any block-level element. The example provided by the CSS2 standards team shows the usual "links turn different colors when you hover the mouse over them" effects. Mozilla correctly allows hover to work for any block-level element. IE only allows it to work for links. Mozilla correctly resizes containing elements if the hover defines a different type style. IE doesn't.
Another example is margins. The margin is the whitespace inside the border of an object, between its content and the border. (Padding is outside the border. The "border" is not necessarily a visible object.) Mozilla correctly spaces objects that use this attribute; IE does not. It's frustrating to read the freaking standard only to learn that the most common browser in the world often ignores what it says.
Why the Hell does anyone still use IE?
![[identity profile]](https://www.dreamwidth.org/img/silk/identity/openid.png){kind=small}
no subject
Date: 2003-11-22 12:14 am (UTC)Perhaps one could simply require a truly standards-compliant browser (and maybe mirror mozilla.org into the bargain)? After all, it's not like they cost anything, or are huge security holes, or are inextricable from the OS or anything like that... *sigh* I say use it as leverage to pry your clients out of the "MS only on the desktop" mentality that's killing the internet with virus traffic these days....