Brent... (and others who may be interested in web design)

[symbioidlj]

Have you heard of this?
http://dean.edwards.name/IE7/overview/

IE7 loads and parses all style sheets into a form that Explorer can understand. You can then use most CSS2/CSS3 selectors without having to resort to CSS hacks.

The lightweight script is a single-line inclusion in your HTML/XML document. No alteration of your original markup is necessary. Neither do you have to alter your CSS.

IE7 provides Microsoft Internet Explorer with support for W3C standard CSS and HTML:

* supports the following CSS selectors:
o namespace|selector
o parent > child
o adjacent + sibling
o adjacent ~ sibling
o [attr], [attr="value"], [attr~="value"] etc
o .multiple.classes (fixes bug)
o :hover, :active, :focus (for all elements)
o :first-child, :last-child, only-child, nth-child, nth-last-child
o :root, :empty
o :before/:after/content:
o :lang()
* works with both HTML and XML documents
* supports imported style sheets
* preserves the cascade of the style sheet
* does not alter the document structure
* does not repeatedly query the DOM tree using JavaScript
* uses pure CSS to enforce style sheet rules
* supports the W3C box model in both standards and quirks mode
* supports fixed positioning (flicker free)
* supports PNG alpha transparency
* works for Microsoft Internet Explorer 5+ (Windows only)

Comments

[vesicular.livejournal.com]

Stuff like this is actually pretty lame. How is this any less of a hack than using CSS hacks? Plus it doesn't do anything for IE on Mac, so you're still stuck.

[symbioid.livejournal.com]

well, soooorrrryyyy!

Seriously, don't you think that it would still save you time and pain? I'm not saying you should do it, NOR am I justifying MS for their shit browser.

Personally, I think everyone should code to standards, and then when IE doesn't work, and people whine about it, they can go fuck off or download a real browser.

But... For people who just HAVE to code for both platforms, wouldn't adding a simple script that's already done, much simpler than actually having to code around IE shit? Then all you have to do is code CSS and not fucking hack it yourself. I dunno, I think it's a good idea, but then again, I'm not a real web developer.

[vesicular.livejournal.com]

I'd say no, and I'll give you a couple reasons. One, it doesn't solve the problems in IE/Mac, like I said before, so you'll still need to add hacks to the CSS, which means you have to spend the time doing hacks anyway.

Two, adding all this JS to a page is just not smart. What happens if it conflicts w/ your JS? Or when it significantly slows down the rendering of pages because it has to load some JS? What happens when IE7 does come out, will this break everything? I think there's too many questions. CSS hacks done right are future proof. They're also really simple. I dunno, I guess I just don't trust stuff like this. It's not just an IE problem. Firefox gets stuff wrong too.

[symbioid.livejournal.com]

I'm curious from the designers perspective, what does Firefox fuck up in rendering? I've not heard any issues, but I'd like to learn.

This is great to hear this from your perspective. Like, nice to learn a bit more than just basic coding. Later Biyatch!

[vesicular.livejournal.com]

No fullscreen support on Mac for one. That one pisses me off all the time. Can't think of any others off hand, but I know there are a couple minor ones. There are various things that work different in Safari and Firefox, even though both will say they follow the W3C. It's just that the W3C spec is so vague in spots, people have to guess what it means some of the time.