- From: Alan Stearns <stearns@adobe.com>
- Date: Fri, 27 Sep 2013 16:14:42 -0700
- To: François REMY <francois.remy.dev@outlook.com>, "www-style@w3.org" <www-style@w3.org>
- CC: Elliott Sprehn <esprehn@gmail.com>
On 9/27/13 4:02 PM, "François REMY" <francois.remy.dev@outlook.com> wrote: >How would you retrieve that Region object? One way would be NamedFlow.getRegions(). But perhaps we should add an attribute to the Element interface as well. > >Another option would be to restrict region properties in pseudo-elements >for now, and stick with the original design. Are there really convincing >use-cases we should have right now that lead us to want to allow regions >inside ::before or ::after at this time? Because if not, we can keep the >Region interface and implement it on Element... and wait for >CSSPseudoElement to appear. That's where we are now. I'm concerned that once CSSPseudoElement appears, we would not be able to have it implement the current Region interface. And there's a real possibility that CSSPseudoElement *never* makes an appearance. I think ::before and ::after regions is useful in itself, but the main thing is that I want to be compatible with *any* future box-generation mechanism in CSS. The proposed change would allow this compatibility up-front, without having to wait for CSSOM for pseudo-elements. And it matches the extensions implemented/proposed for pseudo-elements interacting with events. Thanks, Alan
Received on Friday, 27 September 2013 23:15:09 UTC