W3C home > Mailing lists > Public > www-style@w3.org > February 2014

Procedural (non-technical) point about freezing the cat and hat combinators before they've even been defined (was Re: Shadow DOM: Hat and Cat -- if that's your real name.)

From: Edward O'Connor <eoconnor@apple.com>
Date: Tue, 04 Feb 2014 18:22:33 -0800
To: www-style@w3.org, www-archive@w3.org
Message-id: <m21tzicn86.fsf_-_@eoconnor.apple.com>
+www-archive, replies just to www-archive (since this non-technical)


Tab wrote:

> Chrome *will* be shipping Shadow DOM publicly (in conjunction with
> Moz) in the *very near* future. Whatever API gets shipped will be
> frozen almost immediately. If you want to suggest name changes, as we
> brainstormed a bit at the f2f, do so RIGHT NOW or forever hold your
> peace.

In the CSS WG we've historically allowed implementations to ship
unprefixed properties when the spec containing those properties hits CR.
Selector combinators are a funny case—they can't be prefixed—so we
should be extra careful about shipping them prematurely.

But as far as I can tell, these combinators *aren't even specced*, much
less in a spec that's hit (or will soon hit) CR. This seems highly

I assumed ^ and ^^ would be defined in Selectors 4. But they're not in
its latest WD:


Nor in its latest ED:


Nor are they in the latest Shadow DOM WD:


Nor in its ED:


No, wait, they're in there. In Chapter 6 "Styles" we find this:

> Hats, ^, and Cats, ^^, selector combinators should be defined in this
> section.

I'm left with the conclusion that these combinators are entirely
undefined. I'm really surprised the Chrome team intends to ship these
enabled by default in production.

Received on Wednesday, 5 February 2014 02:22:42 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 11 February 2015 12:35:39 UTC