Differences

This shows you the differences between two versions of the page.

--- spec:css3-regions:regions-styling [2012/03/16 10:21] – vhardy
+++ spec:css3-regions:regions-styling [2014/12/09 15:48] (current) – external edit 127.0.0.1
@@ Line 1: / Line 1: @@
 ==== Region Styling: Proposed alternate syntax ====
+PAGE OBSOLETE: in light of the discussion on www-style (see http://lists.w3.org/Archives/Public/www-style/2012Mar/0490.html), there seem to be a
+preference for sticking to the @region syntax. The getComputedStyle API can be provided differently, for example as a method on the
+Region interface (e.g., Region.getComputedStyle(elem)).
 == Problem Description ==
@@ Line 75: / Line 79: @@
 === Open questions ===
+  * Limitation: styling pseudo elements
+According to the [[http://dev.w3.org/csswg/selectors3/#w3cselgrammar|Selectors Level 3]] specification:
+<file>
+... pseudo-elements are restricted to one per selector and occur only in the last simple_selector_sequence.
+</file>
+which prevents the combination of a '::before' pseudo-element selector with another '::in-region()' pseudo selector.
+In a situation like:
+<code>
+#myElement {
+    flow-into: article;
+}
+#myElement::before {
+    content: "The quick brown fox";
+}
+</code>
+There is no way to select the fragment of #myElement::before that falls into, say, regionA. That selector would be:
+<code>
+#myElement::before::in-region(regionA);
+</code>
+but that would require combining pseudo-elements, which is not possible currently with Selector 3.
+Proposal: accept the limitation of Selector 3. If that gets lifted in Selector 4, authors will get more flexibility.
   * Limitation: nested regions.