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

Re: Proposal of @ua

From: Garrett Smith <dhtmlkitchen@gmail.com>
Date: Sun, 25 Nov 2007 23:27:19 -0800
Message-ID: <c9e12660711252327n48e98ec4o61b4d5661cee5806@mail.gmail.com>
To: "Brad Kemper" <brkemper@comcast.net>
Cc: jesse@dutchmoney.com, "WWW Style" <www-style@w3.org>

On 11/25/07, Brad Kemper <brkemper@comcast.net> wrote:
>
> No, that won't get you very far, because even a UA that claims to
> support a property may support it differently from the others, or may
> not support all the same possible values. For instance, IE doesn't
> support "inherit" as a value of any property, and has different
> visual results on some properties based on whether the element "has
> layout".
I think "inherit" was one of the primary features mentioned in the
beginning of the earliest CSS drafts (c. mid-90's).

Frustrating that IE doesn't support "inherit", isn't it?

I remember getting JScript errors when attempting to set
style.borderColor = "inherit". I can't repro that on my Mac now...

>
> For more about that, and for a sample of the frustration authors feel
> when they try to work around it, check out these pages:
>
> http://www.sitepoint.com/blogs/2007/11/22/in-all-fairness--internet-
> explorer-still-stinks/
>
> http://www.webdevout.net/browser-support-css#support-css2propsbasic
> (be sure to mouse over the yellow rectangles)
This page needs tests.

The page also claims that IE6 supports .class selector, but the
support is broken; considering combined selectors:

.foo.bar

class="foo"

IE 6 misses.
http://blogs.msdn.com/ie/archive/2005/09/02/460115.aspx

>
> In some cases you might even have to know if the browser supported
> some (possibly proprietary) feature of HTML, such as Webkit's
> "placeholder" or "type=search" atributes on INPUTs.
>
Introspection of css features sounds useful.

>
>
> On Nov 22, 2007, at 5:30 PM, jesse von doom wrote:
>
> >
> > But it seems like you don't really care about detecting the user
> > agent *or* rendering engine. You're looking for support for
> > specific CSS functionality. Given that, wouldn't something more
> > like this be in order:
> >
> > @supports multiple-background-image {}
> >
Interesting idea.


...
> >
> > It seems to me that @ua would solve a problem but introduce
> > another, whereas querying for capabilities would only solve a
> > problem, and support smaller browser-makers too.
> >
>
@ua would cause a few problems in attempt to solve a problem.


>
>

-- 
Monkey, so they say, is the root of all people today.
Received on Monday, 26 November 2007 07:27:35 GMT

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