Skip to content

Commit 5db6c94

Browse files
astearnsastearns
committed
[css-regions] Move event triggers to end of visual processing steps
1 parent c29a28b commit 5db6c94

2 files changed

Lines changed: 34 additions & 37 deletions

File tree

‎css-regions/Overview.html‎

Lines changed: 11 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@
1212
rel=dcterms.rights>
1313
<meta content="CSS Regions Module Level 3" name=dcterms.title>
1414
<meta content=text name=dcterms.type>
15-
<meta content=2013-04-22 name=dcterms.date>
15+
<meta content=2013-05-03 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>
@@ -50,7 +50,7 @@
5050

5151
<h1 id=css-regions-module>CSS Regions Module Level 3</h1>
5252

53-
<h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 22 April 2013</h2>
53+
<h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 3 May 2013</h2>
5454

5555
<dl>
5656
<dt>This version:
@@ -2232,19 +2232,8 @@ <h3 id=named-flow-events><span class=secno>6.4. </span>Named flow events</h3>
22322232
are <a
22332233
href="http://www.w3.org/TR/dom/#interface-eventtarget">EventTargets</a>
22342234
which dispatch the following events for their respective triggers. These
2235-
events are asynchronous, and fire in the same step of the <a
2236-
href="http://www.w3.org/TR/html5/webappapis.html#processing-model-2">event
2237-
loop</a> <a href="#HTML5" rel=biblioentry>[HTML5]<!--{{!HTML5}}--></a> as
2238-
when <a
2239-
href="http://www.w3.org/TR/2012/WD-dom-20120405/#mutation-observers">MutationObservers</a>
2240-
<a href="#DOM" rel=biblioentry>[DOM]<!--{{!DOM}}--></a> are invoked.
2241-
2242-
<p>If region chain nesting occurs (the contents of a <a
2243-
href="#dom-named-flow"><code class=idl>NamedFlow</code></a> contains
2244-
regions for a different <a href="#dom-named-flow"><code
2245-
class=idl>NamedFlow</code></a>) then the events for the nested flow(s)
2246-
must be dispatched before the events for the containing flow are
2247-
dispatched.
2235+
events are asynchronous, and fire at the end of the <a
2236+
href="#named-flows-layout">regions visual formatting</a> steps.
22482237

22492238
<p>The regionfragmentchange event is dispatched on any change to a named
22502239
flow's fragmentation through its region chain, including changes to any
@@ -2298,7 +2287,7 @@ <h3 id=named-flow-events><span class=secno>6.4. </span>Named flow events</h3>
22982287
<ul>
22992288
<li><code class=attribute-name>Event.target</code>: <a
23002289
href="#dom-named-flow"><code class=idl>NamedFlow</code></a> whose
2301-
fragmentation may have changed.
2290+
fragmentation has changed.
23022291
</ul>
23032292
</table>
23042293

@@ -2603,6 +2592,10 @@ <h4 id=named-flows-layout><span class=secno>7.2.3. </span>Step 3: named
26032592
out in the outer region chain. Once Step 3 for an outer named flow is
26042593
complete, Step 3 for the inner named flows recursively begins.
26052594

2595+
<p>Once Step 3 for a named flow is complete, The conditions for the <a
2596+
href="#named-flow-events">named flow events</a> are checked, and if the
2597+
triggers are met the events dispatch at this point.
2598+
26062599
<div class=note>
26072600
<p>The model for resolving auto sized regions will cause, under certain
26082601
circumstances, the flow content to be overset or underset. In other
@@ -3021,6 +3014,8 @@ <h3 id="changes_from_Aug_28_2012"><span class=secno>12.1. </span>Changes
30213014
28<sup>th</sup> 2012</a> version</h3>
30223015

30233016
<ul>
3017+
<li>Tied named flow event triggers to visual processing model
3018+
30243019
<li>Described how visual formatting of nested regions works
30253020

30263021
<li>Added regionoversetchange event

‎css-regions/Overview.src.html‎

Lines changed: 23 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -2057,21 +2057,9 @@ <h3 id="named-flow-events">Named flow events</h3>
20572057
which dispatch the following events
20582058
for their respective triggers.
20592059
These events are asynchronous,
2060-
and fire in the same step of the
2061-
<a href="http://www.w3.org/TR/html5/webappapis.html#processing-model-2">event loop</a>
2062-
[[!HTML5]] as when
2063-
<a href="http://www.w3.org/TR/2012/WD-dom-20120405/#mutation-observers">MutationObservers</a>
2064-
[[!DOM]] are invoked.</p>
2065-
<p>If region chain nesting occurs
2066-
(the contents of a <a href="#dom-named-flow"><code class="idl">NamedFlow</code></a>
2067-
contains regions
2068-
for a different <a href="#dom-named-flow"><code class="idl">NamedFlow</code></a>)
2069-
then the events
2070-
for the nested flow(s)
2071-
must be dispatched
2072-
before the events
2073-
for the containing flow
2074-
are dispatched.</p>
2060+
and fire at the end of the
2061+
<a href="#named-flows-layout">regions visual formatting</a>
2062+
steps.</p>
20752063

20762064
<p>The regionfragmentchange event is dispatched on any change to a named flow's fragmentation through its region chain, including changes to any overset fragment.</p>
20772065

@@ -2094,7 +2082,7 @@ <h3 id="named-flow-events">Named flow events</h3>
20942082
<td>
20952083
<ul>
20962084
<li><code class="attribute-name">Event.target</code>:
2097-
<a href="#dom-named-flow"><code class="idl">NamedFlow</code></a> whose fragmentation may have changed.
2085+
<a href="#dom-named-flow"><code class="idl">NamedFlow</code></a> whose fragmentation has changed.
20982086
</li>
20992087
</ul>
21002088
</td>
@@ -2344,12 +2332,25 @@ <h4 id="named-flows-layout">Step 3: named flows layout</h4>
23442332
Once Step 3 for an outer named flow is complete,
23452333
Step 3 for the inner named flows recursively begins.</p>
23462334

2335+
<p>Once Step 3 for a named flow is complete,
2336+
The conditions for the
2337+
<a href="#named-flow-events">named flow events</a> are checked,
2338+
and if the triggers are met
2339+
the events dispatch at this point.</p>
2340+
23472341
<div class="note">
2348-
<p>The model for resolving auto sized regions will cause, under certain circumstances,
2349-
the flow content to be overset or underset. In other words, it will not fit tightly.
2350-
The model prevents having circular dependencies in the layout model. Implementations
2351-
may decide to apply further layout steps to ensure that the whole flow content is
2352-
displayed to the user, even in edge cases.</p>
2342+
<p>The model for resolving auto sized regions will cause,
2343+
under certain circumstances,
2344+
the flow content to be overset or underset.
2345+
In other words,
2346+
it will not fit tightly.
2347+
The model prevents having circular dependencies
2348+
in the layout model.
2349+
Implementations may decide to apply
2350+
further layout steps
2351+
to ensure that the whole flow content
2352+
is displayed to the user,
2353+
even in edge cases.</p>
23532354
</div>
23542355

23552356
<h3 id="regions-visual-formatting-implementation-note">Regions visual formatting: implementation note</h3>
@@ -2587,6 +2588,7 @@ <h2 id="changes">Changes</h2>
25872588
<h3 id="changes_from_Aug_28_2012">Changes from <a href="http://www.w3.org/TR/2012/WD-css3-regions-20120823/">August 28<sup>th</sup> 2012</a> version</h3>
25882589

25892590
<ul>
2591+
<li>Tied named flow event triggers to visual processing model</li>
25902592
<li>Described how visual formatting of nested regions works</li>
25912593
<li>Added regionoversetchange event</li>
25922594
<li>renamed regionlayoutupdate to regionfragmentchange</li>

0 commit comments

Comments
 (0)