Sent by Alan Gresley on 18 July 2009 17:05
Philippe Wittenbergh wrote:
>
> Just 2 notes on this:
>
> On Jul 17, 2009, at 3:29 PM, Alan Gresley wrote:
>
>> I would not recommend
>> hacking your HTML with IE Conditional comments since they are not in one
>> location and thus not easily removed.
>
>
> 1. If your website is larger than 3 pages and reuses the same
> stylesheets, I hope you use server-side templates :-). From the humble
> (yet quite powerful) SSI to PHP, ASP or other name-you-favourite server
> side language, an include to load your block of <link rel="stylesheet"
> ...> with CC's in it.
Hello Philippe,
Yes I do use server side includes which I would place CC comments in if
needed. This I do not frown on since it's centralized.
I only state this issue about CC because coders who are new to this list
may pollute their non server-side templates or standard HTML with CC on
the advice that CC are ok to use. The whole <head> element or elements
within the <head> element can be server-side templates.
> No need for support for IE anymore? Just remove a couple of lines out of
> that include, upload done. Let the server do the rest of the job.
>
> 2. multiple @imports and nested constructs:
>
> On Jul 18, 2009, at 12:31 AM, Alan Gresley wrote:
>
>> My regular CSS,
>>
>> <http://css-class.com/test/epsilon-0-1.css>
>
> You do know that such constructs are detrimental to performance and page
> load, esp. in IE, do you?
Internet Explorer is a detriment to the progress (interoperability) of
the of the Internet or Intranet. Surely this list isn't here just to
nurse *that browser* along.
Is the detriment to performance balanced by the lessor code that is is
in the CSS and HTML. Yes the CSS is targeting many elements at once but
the matching of this against ids' or classes in the HTML is not needed.
> Fex:
> http://www.stevesouders.com/blog/2009/04/09/dont-use-import/
> take this with a grain of salt, but I did some similar tests with IE
> running on an older machine, and multiple @imports do slow down things.
>
> My 2¥,
>
> Philippe
> ---
> Philippe Wittenbergh
> http://l-c-n.com/
I accept your point of view Philippe. I do like to help others with IE7
at least. But I see that the continue focus of a legacy does hold back
where CSS can go. I not saying that my method is a good way, just that
it is an option. My used of @imports is just to support IE7 or lower. I
have been influenced by Georg and his masterpiece.
http://www.gunlaug.no/contents/wd_1_02_01.html
I just see no point in compromising ones code just to fit in with IE
bugs and legacy behavior.
--
Alan http://css-class.com/
Armies Cannot Stop An Idea Whose Time Has Come. - Victor Hugo
______________________________________________________________________
css-discuss [EMAIL-REMOVED]]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
