- From: Dimitri Glazkov <dglazkov@google.com>
- Date: Tue, 10 Sep 2013 09:14:38 -0700
- To: Jonas Sicking <jonas@sicking.cc>
- Cc: public-webapps <public-webapps@w3.org>, Steve Orvell <sorvell@google.com>, Scott Miles <sjmiles@google.com>, Blake Kaplan <mrbkap@mozilla.com>, Elliott Sprehn <esprehn@gmail.com>, Dominic Cooney <dominicc@google.com>, William Chen <wchen@mozilla.com>, "Tab Atkins Jr." <jackalmage@gmail.com>, fantasai <fantasai@inkedblade.net>, David Baron <dbaron@dbaron.org>
On Tue, Sep 10, 2013 at 6:54 AM, Jonas Sicking <jonas@sicking.cc> wrote: > On Tue, Sep 10, 2013 at 1:32 AM, Dimitri Glazkov <dglazkov@google.com> wrote: >> To calm the brave guinea people down, I showed them a magic trick. Out >> of my sleeve, I pulled out two new combinators: A hat (^) and a cat >> (^^). > > The syntax here certainly looks interesting. However how are we > planning on supporting things like styling built-in form controls? It > would be very nice to enable styling the dropdown of a <select> using > the same CSS selector whether the <select> has been implemented using > C++, a built-in WebComponent or a library-supplied WebComponent. This is a great point and something I attempted to argue for at the recent Shadow DOM styling meeting. However, dbaron@ basically said that we shouldn't conflate native controls styling with shadow DOM (http://www.w3.org/2013/06/21-webapps-minutes.html, search for "native anonymous content"), and then other folks chimed in agreeing with this position, so I let that go. The "::part" is already a compromise in this regard, since it does not explain how the magic behind things like ::placeholder. :DG<
Received on Tuesday, 10 September 2013 16:15:09 UTC