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

Re: [css-forms][css-ui] Styling native components, a proposal

From: Brad Kemper <brad.kemper@gmail.com>
Date: Sun, 27 Mar 2016 10:26:31 -0700
Cc: Lea Verou <lea@verou.me>, www-style list <www-style@w3.org>
Message-Id: <ADABCC40-326F-41A8-BA5E-3BE20BE57A30@gmail.com>
To: Amelia Bellamy-Royds <amelia.bellamy.royds@gmail.com>
Yes, those hacks do exist, and are not invalid, and are necessary sometimes. Changing that for existing pseudos would break layouts. It would be OK for new pseudos though, I think.

> On Mar 26, 2016, at 6:14 PM, Amelia Bellamy-Royds <amelia.bellamy.royds@gmail.com> wrote:
> 
> I realize that suggesting a change to the fundamental CSS parsing rules could have wide-reaching implications.  However, I'd be interested in whether anyone can come up with practical examples where changing an invalid selector to a valid-but-doesn't-match-anything selector would break existing code.  Possibly there are horrible hacks for targetting CSS to specific browsers that rely on this behavior, but that's all I can think of.


Received on Sunday, 27 March 2016 17:27:00 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:09:01 UTC