Yes, I recall hearing something about this in one of the discussions
long ago, or on some article or commit.
The original reason for using @import was to separate the CSS1 from the
CSS2 rather than sending a CSS1 browser a lot of CSS2 which may break
styles since only half of it is actually understood, and it won't
validate right at all.
~Daniel Friesen(Dantman) of:
-The Nadir-Point Group (
)
--Games-G.P.S. (
On Thu, Jun 12, 2008 at 2:46 PM, Huji
<huji.huji(a)gmail.com> wrote:
Actually, using @import has another side effect
too: When saving the page,
not all CSS is saved (depends on browser, of course). Using link makes sure
that all CSS is going to be saved.
So unless a robust technical reason is given, I'm in support of getting rid
of @imports (only because they're supported and classy, doesn't mean they
should be used).
Note that CSS1 user agents will obey <link> but ignore @import, since
the latter was not part of CSS1. I'm pretty sure this was part of the
original rationale for using @import in some places. This should be
considered before changing it. CSS1 user agents are probably not a
huge concern anymore, but I'm guessing that CSS1 user agents that try
to read CSS2.1 written with no regard for CSS1 compatibility will end
up ignoring half the rules and displaying a total mess.
_______________________________________________
Wikitech-l mailing list
Wikitech-l(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l