Ok, I added the Jackie Brown part.
From the movie.

As in:

"When you absolutely, positively have to kill every last Mother #$%^ CSS bug in the room - Rafael Lima's CSS browser specific selector!

There is no substitute."

http://github.com/rafaelp/css_browse...or/tree/master
http://rafael.adm.br/css_browser_selector/

He just saved me a lot of headache so I needed to share.

and what happens if js is disabled in the browser?

Originally Posted by davemies

and what happens if js is disabled in the browser?

Fair point.
But to be perfectly honest,
this is not 1999, its 2009.

JavaScript is a basic enabling technology of Web 2.0
Last time I checked, I couldn't even log into Hotmail if JS was
disabled in the browser.

So I think anybody who chooses to turn off JavaScript is in
the same league as anyone who chooses to keep running IE6.
You do so at your own risk.

Having said that, of course one needs to be mindful about people
using assistive technology for accessibility.
But if we are talking about JS simply for fine tuned CSS targeting
I don't think THAT is really an issue.

i agree but i'm thinking of controlled environments, where end users have no say what runs on their system - say like the same businesses running ie6 that have everything locked down tighter than a tight thing. it's just good just to test that what you have left with no js works ok

looks very interesting though!

Originally Posted by davemies

i agree but i'm thinking of controlled environments, where end users have no say what runs on their system - say like the same businesses running ie6 that have everything locked down tighter than a tight thing. it's just good just to test that what you have left with no js works ok

looks very interesting though!

Yep. Totally.
I think this is kind of a tool of last resort.
Fixing cross browser CSS bugs can be a swine of a job as
we all know.

Actually I found this when I was looking for a way to target the WebKit
layout engine (Chrome and Safari).
We used to be able to use the "nth child" selector hack but now that
Firefox 3.5 recognizes that CSS attribute, its not useful anymore.