- From: Anne van Kesteren <annevk@annevk.nl>
- Date: Tue, 10 Dec 2013 16:15:25 +0000
- To: Domenic Denicola <domenic@domenicdenicola.com>
- Cc: Erik Arvidsson <arv@chromium.org>, Dominic Cooney <dominicc@google.com>, Ryosuke Niwa <rniwa@apple.com>, Hajime Morrita <morrita@google.com>, Dimitri Glazkov <dglazkov@chromium.org>, "public-webapps@w3.org WG" <public-webapps@w3.org>, Jan Miksovsky <jan@quickui.org>
On Tue, Dec 10, 2013 at 4:10 PM, Domenic Denicola <domenic@domenicdenicola.com> wrote: > Nevertheless, it would be unfortunate to use the in-progress nature of making the web platform more JavaScript-friendly as an argument for making it more JavaScript hostile (by prohibiting element subclassing). Well, the question is more what we should focus on first and whether doing it in the wrong order will be future hostile. I'm also somewhat skeptical that if we don't go through the exercise of explaining a couple of existing elements first, the generic mechanism they are all supposed to end up with will be correct. -- http://annevankesteren.nl/
Received on Tuesday, 10 December 2013 16:15:56 UTC