- From: <bugzilla@jessica.w3.org>
- Date: Wed, 05 Jun 2013 06:50:43 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=22268
Dominic Cooney <dominicc@chromium.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dominicc@chromium.org
--- Comment #1 from Dominic Cooney <dominicc@chromium.org> ---
You may be able to work around this problem by using CSS Regions.
Two slightly more powerful mechanisms than the proposal to make <content>
happen "last" are:
1. Distribute to <content> elements not in document order, but in selector
specificity order. Make <content> with no selector less specific than any
selector. Document order of <content> element is a fallback for tiebreaking.
2. Let the author separately specify an order to do distribution.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Wednesday, 5 June 2013 06:50:44 UTC