- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Mon, 9 Sep 2013 18:31:10 -0700
- To: Scott Miles <sjmiles@google.com>
- Cc: Dimitri Glazkov <dglazkov@google.com>, public-webapps <public-webapps@w3.org>, Steve Orvell <sorvell@google.com>, Blake Kaplan <mrbkap@mozilla.com>, Elliott Sprehn <esprehn@gmail.com>, Dominic Cooney <dominicc@google.com>, William Chen <wchen@mozilla.com>, fantasai <fantasai@inkedblade.net>, David Baron <dbaron@dbaron.org>
On Mon, Sep 9, 2013 at 6:20 PM, Scott Miles <sjmiles@google.com> wrote: >>> I'd greatly prefer to stick with the current plan of having to mark >>> things to be exposed explicitly, > > Fwiw, we tried that and got in the weeds right away. See Dimitri's post for > details. I'm afraid of trading real-life pain (e.g. exploding part lists) > for what is IMO an unreal advantage (e.g. the notion components can be > upgraded and assured never to break is just not realistic). Did you miss my suggestion that we allow this with a third value on the current "allow selectors through" switch? ~TJ
Received on Tuesday, 10 September 2013 01:31:57 UTC