- From: Simon Pieters <simonp@opera.com>
- Date: Tue, 01 Oct 2013 00:45:04 +0200
- To: "www-style@w3.org" <www-style@w3.org>, "Alan Stearns" <stearns@adobe.com>
- Cc: "Elliott Sprehn" <esprehn@gmail.com>
On Mon, 30 Sep 2013 17:50:26 +0200, Alan Stearns <stearns@adobe.com> wrote: > It seems odd that I can get from an Element to a PseudoElement, but > there's no way to get back from the PseudoElement to the Element (or find > out which PseudoElement it is). Am I missing something? It hasn't beed added yet because none of these points from the end of the email below have been met yet, AFAIK: http://lists.w3.org/Archives/Public/www-style/2013Aug/0453.html > In any case, it's easy enough to say in a spec: > > Element implements Region > PseudoElement implements Region > > But the question then is what happens with the NamedFlow.getRegions() > call, which is intended to return a sequence of Regions. If those Regions > can be either an Element or a PseudoElement, what then? You can make the return value sequence<(Region or Element or PseudoElement)> > Either we need to > have a common base class that both Element and PseudoElement can inherit > from, or we have to introduce multiple inheritance. Neither of those > options appear feasible in the WebKit/Blink codebase (for this one small > use case, at least). > > So it seems to me that making Region a standalone interface would be a > better, incremental step. > > Thanks, > > Alan > -- Simon Pieters Opera Software
Received on Monday, 30 September 2013 22:45:38 UTC