Zero Piraeus wrote:
> ... I'm specifically wondering why the [as far as I can tell]
> preferred resources for filtering with @import recommend a method
> that is reportedly disastrous for some browsers.
Probably because so many just follow recommendations and copy "best
practices" or something - rather than try figuring out how things work.
Figuring out browsers take time, although we most often only have to do
it once.
I never use @import in page-heads. Links do a perfect job there. That
@import rule is heavily used in my stylesheets though.
---
If proper use of any standard rule does indeed crash a browser -
old and outdated or completely new one - then that's a weak spot in that
browser and not in the page-code.
For a new browser we may report weak spots, so whoever is responsible
can fix that "thing".
Old browsers are either overlooked or worked around, depending on how
important each of us - or some client - think it is to support its
users. Browsers are irrelevant in themselves, IMO.
---
Must be a years since I looked at anything in NN4, but that's another
matter since NN4 doesn't get any styles from me anyway because I use
@media rules in my stylesheets. That's an unintentional side-effect of a
very intentional use of specs, but one that I am perfectly aware of :-)
So, yes, awareness is important when any rules are applied. Using
regular rules as hacks can be a dangerous business.
regards
Georg
--
http://www.gunlaug.no
______________________________________________________________________
css-discuss [EMAIL PROTECTED]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
