This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
spec:css3-regions:regions-styling [2012/03/16 09:54] – astearns | spec:css3-regions:regions-styling [2012/03/16 10:21] – vhardy | ||
---|---|---|---|
Line 51: | Line 51: | ||
The issues with the current @region rule are: | The issues with the current @region rule are: | ||
- | - requires additional DOM interfaces to access the @rule | + | - requires |
- is not consistent with :: | - is not consistent with :: | ||
- inconsistency between the CSS syntax (@region) and the getComputedStyle calls (use ':: | - inconsistency between the CSS syntax (@region) and the getComputedStyle calls (use ':: | ||
Line 76: | Line 76: | ||
=== Open questions === | === Open questions === | ||
- | * Can we chain pseudo-elements? | + | * Limitation: nested regions. |
+ | |||
+ | Consider | ||
< | < | ||
- | window.getComputedStyle(elem, | + | <div id="postit-A"></ |
+ | <div id=" | ||
+ | |||
+ | <div id="regionA" | ||
+ | <div id=" | ||
+ | <div id=" | ||
+ | <div id=" | ||
+ | |||
+ | #postit-A, #postit-B { | ||
+ | flow-from: block-flow; | ||
+ | } | ||
+ | |||
+ | #regionA, #regionB, #regionC, #regionD { | ||
+ | flow-into: block-flow; | ||
+ | flow-from: article; | ||
+ | } | ||
</ | </ | ||
- | According | + | What if we want to have special styling for a '.title' |
- | + | ||
- | < | + | .title:: |
- | Note that pseudo-elements are restricted to one per selector and occur only in the last simple_selector_sequence. | + | into the fragment of regionB that falls into postit-A. |
- | </ | + | |
- | which seems to prevent the combination of a ':: | + | Proposed resolution: accept this limitation. |