W3C home > Mailing lists > Public > www-style@w3.org > August 2012

Re: [css3-conditional] navigator.supportsCSS rather than window.supportsCSS

From: Elliott Sprehn <esprehn@gmail.com>
Date: Tue, 14 Aug 2012 23:37:43 -0700
Message-ID: <CAPJYB1ivttX85ZF-w16xq5mL1EDe7VkJLRXtEgxzqb_Hxi9=Eg@mail.gmail.com>
To: "Tab Atkins Jr." <jackalmage@gmail.com>
Cc: Boris Zbarsky <bzbarsky@mit.edu>, Glenn Adams <glenn@skynav.com>, www-style list <www-style@w3.org>
On Wed, Aug 8, 2012 at 9:40 AM, Tab Atkins Jr. <jackalmage@gmail.com> wrote:

> So, based on the discussions on this thread, what does the group feel
> about defining a new global named "CSS", which we use to hang new
> css-related things off of that may not be worth polluting the global
> object with (or that would require a cumbersome name if they were put
> on the global).
I don't like this idea. There's nothing like this in the platform yet, and
the difference between CSS.PixelValue and CSSPixelValue is one letter.

Either way, supports() really needs to be a document level feature anyway
because browsers support different CSS properties in standards vs quirks
mode (IE...), or even in extensions or apps vs web pages (ex -moz-binding).

document.supportsCSS(property, value) is what you want.

- E
Received on Wednesday, 15 August 2012 06:38:30 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:20 UTC