W3C home > Mailing lists > Public > www-style@w3.org > November 2007

Re: Proposal of @ua

From: Brad Kemper <brkemper@comcast.net>
Date: Tue, 27 Nov 2007 23:18:31 -0800
Message-Id: <623D74B3-73BF-4B62-8ED4-2153E82E786B@comcast.net>
Cc: Alan Gresley <alan1@azzurum.com>, www-style@w3.org
To: Andrew Fedoniouk <news@terrainformatica.com>

On Nov 27, 2007, at 10:41 AM, Andrew Fedoniouk wrote:

>> you would be able to apply the same line of code like this (if IE8  
>> supported this sort of media query):
>>
>> @media screen and (renderer:Trident) {
>>  a.exlink {display:inline-block;}
>> }
> I suggest to add support(attribute[,value]) function instead.
>
> So this:
>
> @media screen and has(renderer:Trident)
> {
>    a.exlink {display:inline-block;}
> }
>
> can be rewritten as
>
> @media screen and support( display, inline-block  )
> {
>    a.exlink {display:inline-block;}
> }
> @else
> {
>    a.exlink {display:block; }
> }
>
> This construction will match IE6, IE7, Opera but not FF2 as IE and  
> Opera do have support of inline-block.
> (IE supports it partially, only for <span> alike elements, but still)

It is exactly that word "partially" that makes such a proposal of  
very limited use. It might be worthwhile for as far as it goes, but  
it doesn't go far enough precisely because of support that is  
incomplete. I've mentioned a couple, such as how some values cause  
changes to the meaning of z-axis, and some things when gaining  
dimension cause all manner of weirdness, including to descendants.  
For many other places where support for a particular browser is  
partial, pay attention to the yellow rectangles on the following page  
that compares IE6, IE7, FireFox 2, and Opera 9:

http://www.webdevout.net/browser-support-css#support-css2propsbasic
Received on Wednesday, 28 November 2007 07:18:56 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 27 April 2009 13:54:56 GMT