- From: François REMY <francois.remy.dev@outlook.com>
- Date: Mon, 20 May 2013 18:23:22 +0200
- To: Brad Kemper <brad.kemper@gmail.com>
- CC: Hċkon Wium Lie <howcome@opera.com>, Tab Atkins Jr. <jackalmage@gmail.com>, Alan Stearns <stearns@adobe.com>, Sylvain Galineau <galineau@adobe.com>, "www-style@w3.org" <www-style@w3.org>
> I agree that the combinator approach looks and works better than the pseudo-element approach. But it seems a bit overkill to create a whole new combinator, just for use with regions only. My definition of '...' is more general than just regions: it's meant to match the descendant of an element in the layout tree, and '...>' matches the direct children of an element in the layout tree. So it would replace ::distributed() as well and probably other insertion mechanisms in the future. But maybe that don't work in practice. > Also, of the examples you gave, the @region version had the best combination of compactness (once you remove the unnecessary ':scope' parts) and DRY-ness. And to my eye is the clearest. I included the :scope part because I suspect the most common case will be to select direct children, in which case you'll need :scope.
Received on Monday, 20 May 2013 16:23:54 UTC