W3C home > Mailing lists > Public > www-style@w3.org > March 2015

Re: Domain selectors

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Wed, 11 Mar 2015 14:51:24 -0700
Message-ID: <CAAWBYDATz3quXh4tiO5Q0Cw9qt8qhV6Pj_1P7NsYDtwZg-6psw@mail.gmail.com>
To: Jens Oliver Meiert <jens@meiert.com>
Cc: Marat Tanalin <mtanalin@yandex.ru>, "L. David Baron" <dbaron@dbaron.org>, W3C WWW Style <www-style@w3.org>
On Tue, Mar 10, 2015 at 9:29 AM, Jens Oliver Meiert <jens@meiert.com> wrote:
>> What Marat said. Don't try to reuse existing syntaxes for incompatible
>> things; it's just confusing for everyone.  For the same reason, the
>> pseudo-element approach is out, unless there's *actually some
>> pseudo-element in the page that it corresponds to*.
>> @-rules are how we introduce arbitrary new block-based syntax.  Other
>> than the exact characters used, there is literally no difference
>> between "@document domain("foo") { h1 { color: red; } }" and
>> "[host="foo"] h1 { color: red; }"; the two are expressing identical
>> semantics, so there's no actual benefit in reaching for the one that
>> misuses the syntax.
> If I was as upset I’d point out that “other than the exact characters
> used there is no difference” is quite a statement, one that you alone
> has probably ripped apart a good number of times :)

Oh, definitely; I was responding to your earlier statements implying
there was a functional difference:

> @document doesn’t seem to be much of an advantage
> over just using a separate style sheet, an option always
> at our disposal, whereas [host=], as a selector, would
> allow for easy, DRY domain-specific adjustments.

Received on Wednesday, 11 March 2015 21:52:10 UTC

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