- From: Anne van Kesteren <annevk@annevk.nl>
- Date: Thu, 30 Apr 2015 13:43:48 +0200
- To: Ryosuke Niwa <rniwa@apple.com>
- Cc: Hayato Ito <hayato@chromium.org>, WebApps WG <public-webapps@w3.org>, Jan Miksovsky <jan@component.kitchen>
On Tue, Apr 28, 2015 at 7:09 PM, Ryosuke Niwa <rniwa@apple.com> wrote: > The problem with "<shadow> as function" is that the superclass implicitly selects nodes based on a CSS selector so unless the nodes a subclass wants to insert matches exactly what the author of superclass considered, the subclass won't be able to override it. e.g. if the superclass had an insertion point with select="input.foo", then it's not possible for a subclass to then override it with, for example, an input element wrapped in a span. So what if we flipped this as well and came up with an imperative API for "<shadow> as a function". I.e. "<shadow> as an actual function"? Would that give us agreement? It'd be great to have something like this available. -- https://annevankesteren.nl/
Received on Thursday, 30 April 2015 11:44:11 UTC