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

Re: @media and browsers conditional statments

From: Robert O'Callahan <robert@ocallahan.org>
Date: Tue, 5 Aug 2008 12:53:31 +1200
Message-ID: <11e306600808041753h6999b736ga1b1daabb13199ac@mail.gmail.com>
To: Simetrical <simetrical@gmail.com>
Cc: "Francois Remy" <fremycompany_pub@yahoo.fr>, "Benjamin Hawkes-Lewis" <bhawkeslewis@googlemail.com>, "CSS 3 W3C Group" <www-style@w3.org>
On Tue, Aug 5, 2008 at 2:42 AM, Simetrical <simetrical@gmail.com> wrote:

> That's not true.  For instance, latest Gecko does not support @page,
> display: run-in, white-space: pre-line, and probably other CSS2.1
> features.  I don't think any UA "fully supports" CSS2 or CSS2.1 yet.

The *very* latest Gecko (i.e. trunk) does support pre-line :-).

> The extra complexity is trivial even in an absolute sense, and even
> more so when you take into account that it potentially replaces a huge
> array of selector hacks and JavaScript.  (And selector hacks become
> even harder to maintain as browsers become more standardized.)  It
> doesn't get around issues of *old* buggy browsers, but it will help to
> get around issues of *new* buggy browsers.  It's idealistic to suppose
> that there won't be any ever.


"He was pierced for our transgressions, he was crushed for our iniquities;
the punishment that brought us peace was upon him, and by his wounds we are
healed. We all, like sheep, have gone astray, each of us has turned to his
own way; and the LORD has laid on him the iniquity of us all." [Isaiah
Received on Tuesday, 5 August 2008 00:54:08 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:27:39 UTC