1212 rel =dcterms.rights >
1313 < meta content ="CSS Regions Module Level 1 " name =dcterms.title >
1414 < meta content =text name =dcterms.type >
15- < meta content =2013-06-19 name =dcterms.date >
15+ < meta content =2013-06-25 name =dcterms.date >
1616 < meta content ="Vincent Hardy " name =dcterms.creator >
1717 < meta content ="Rossen Atanassov " name =dcterms.creator >
1818 < meta content ="Alan Stearns " name =dcterms.creator >
5050
5151 < h1 id =css-regions-module > CSS Regions Module Level 1</ h1 >
5252
53- < h2 class ="no-num no-toc " id =longstatus-date > Editor's Draft 19 June 2013</ h2 >
53+ < h2 class ="no-num no-toc " id =longstatus-date > Editor's Draft 25 June 2013</ h2 >
5454
5555 < dl >
5656 < dt > This version:
@@ -2051,7 +2051,7 @@ <h3 id=the-region-interface><span class=secno>6.2. </span>The Region
20512051 Region</ span > . The method returns null if the < a
20522052 href ="#css-region "> region</ a > object is not (or no longer) a region.
20532053
2054- < div class =note >
2054+ < div class =note > < span class = note-prefix > Note </ span >
20552055 < p > If the element is not contained in the < span > CSS Region</ span > at all,
20562056 the method returns the < a href ="#the-region-pseudo-element "> region
20572057 styling</ a > that would apply to the element if it were contained in the
@@ -2439,7 +2439,7 @@ <h4 id=named-flows-layout><span class=secno>7.2.3. </span>Step 3: named
24392439 href ="#named-flow-events "> named flow events</ a > are checked, and if the
24402440 triggers are met the events dispatch at this point.
24412441
2442- < div class =note >
2442+ < div class =note > < span class = note-prefix > Note </ span >
24432443 < p > The model for resolving auto sized regions will cause, under certain
24442444 circumstances, the flow content to be overset or underset. In other
24452445 words, it will not fit tightly. The model prevents having circular
@@ -2672,19 +2672,22 @@ <h4 id=step-3-named-flows-layout><span class=secno>7.4.4. </span>Step 3:
26722672 < h2 id =relation-to-document-events > < span class =secno > 8. </ span > Relation to
26732673 document events</ h2 >
26742674
2675- < p > The CSS regions module does not alter the normal processing of events in
2675+ < p > The CSS Regions module does not alter the normal processing of events in
26762676 the document tree. In particular, if an event occurs on an element that is
26772677 part of a < a href ="#named-flow0 "> named flow</ a > , the < a
26782678 href ="http://www.w3.org/TR/dom/#events "> event's bubble and capture
26792679 phases</ a > happen following the document tree order.
26802680
2681- < div class =issue-marker data-bug_id =21132 data-bug_status =ASSIGNED > < a
2682- href ="https://www.w3.org/Bugs/Public/show_bug.cgi?id=21132 "> Issue-21132</ a >
2683-
2684- < div class =issue-details >
2685- < p class =short-desc > Regions need a way to respond to events in their
2686- content fragment
2687- </ div >
2681+ < div class =note > < span class =note-prefix > Note </ span >
2682+ < p > This means that in most cases CSS Regions will not receive user events
2683+ that trigger on their named flow content. Event handlers for named flow
2684+ content can check < code > < a
2685+ href ="http://dev.w3.org/csswg/cssom-view/#extensions-to-the-document-interface "> getElementsFromPoint()</ a > </ code >
2686+ < a href ="#CSSOM-VIEW "
2687+ rel =biblioentry > [CSSOM-VIEW]<!--{{CSSOM-VIEW}}--> </ a > to find the CSS
2688+ Region where the user event occurred. Future versions of CSS-UI may
2689+ provide a more general solution for user event bubbling where the stack
2690+ of elements at the event coordinates may not follow DOM order.
26882691 </ div >
26892692
26902693 < h2 id =relation-to-other-specifications > < span class =secno > 9.
@@ -2708,12 +2711,10 @@ <h2 id=relation-to-other-specifications><span class=secno>9.
27082711
27092712 < li > CSS Exclusions Module < a href ="#CSS3-EXCLUSIONS "
27102713 rel =biblioentry > [CSS3-EXCLUSIONS]<!--{{CSS3-EXCLUSIONS}}--> </ a > . This
2711- module defines a generic way to define arbitrarily shaped exclusions into
2712- which content can flow or around which content can flow. This can be seen
2713- as an extension to the way CSS floats provide rectangular areas into
2714- which content flows and around which content flows. In advanced layout
2715- designs, it is expected that the CSS Exclusions module will be commonly
2716- combined with the CSS regions module.
2714+ module defines a generic way to define exclusions around which content
2715+ can flow. This can be seen as an extension to CSS floats. In advanced
2716+ layout designs, it is expected that the CSS Exclusions module will be
2717+ commonly combined with the CSS Regions module.
27172718
27182719 < li > CSS Line Grid Module < a href ="#CSS3-LINE-GRID "
27192720 rel =biblioentry > [CSS3-LINE-GRID]<!--{{CSS3-LINE-GRID}}--> </ a > . This
@@ -2857,6 +2858,8 @@ <h3 id="changes_from_Aug_28_2012"><span class=secno>12.1. </span>Changes
28572858 28< sup > th</ sup > 2013</ a > version</ h3 >
28582859
28592860 < ul >
2861+ < li > Removed issue on user events and added note describing solution(s)
2862+
28602863 < li > Changed type of NamedFlow.getContent() from NodeList to
28612864 sequence<Node>
28622865 </ ul >
@@ -3270,6 +3273,16 @@ <h3 class=no-num id=other-references>Other references</h3>
32703273 href ="http://www.w3.org/TR/2013/WD-css3-page-20130314/ "> http://www.w3.org/TR/2013/WD-css3-page-20130314/</ a >
32713274 </ dd >
32723275 <!---->
3276+
3277+ < dt id =CSSOM-VIEW > [CSSOM-VIEW]
3278+
3279+ < dd > Anne van Kesteren. < a
3280+ href ="http://www.w3.org/TR/2011/WD-cssom-view-20110804/ "> < cite > CSSOM View
3281+ Module.</ cite > </ a > 4 August 2011. W3C Working Draft. (Work in progress.)
3282+ URL: < a
3283+ href ="http://www.w3.org/TR/2011/WD-cssom-view-20110804/ "> http://www.w3.org/TR/2011/WD-cssom-view-20110804/</ a >
3284+ </ dd >
3285+ <!---->
32733286 </ dl >
32743287 <!--end-informative-->
32753288
0 commit comments