Skip to content

Commit 4d78619

Browse files
astearnsastearns
committed
[regions] change case of regionlayoutupdate
1 parent cde0311 commit 4d78619

2 files changed

Lines changed: 17 additions & 52 deletions

File tree

‎css3-regions/Overview.html‎

Lines changed: 12 additions & 27 deletions
Original file line numberDiff line numberDiff line change
@@ -12,12 +12,12 @@
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=2012-10-19 name=dcterms.issued>
15+
<meta content=2012-11-05 name=dcterms.issued>
1616
<meta content="Vincent Hardy" name=dcterms.creator>
1717
<meta content="Alex Mogilevsky" name=dcterms.creator>
1818
<meta content="Alan Stearns" name=dcterms.creator>
1919
<meta content=W3C name=dcterms.publisher>
20-
<meta content="http://www.w3.org/TR/2012/ED-css3-regions-20121019/"
20+
<meta content="http://www.w3.org/TR/2012/ED-css3-regions-20121105/"
2121
name=dcterms.identifier>
2222
<link href="../shared/style/default.css" rel=stylesheet type="text/css">
2323
<script defer=defer
@@ -50,14 +50,14 @@
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 19 October
53+
<h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 5 November
5454
2012</h2>
5555

5656
<dl>
5757
<dt>This version:
5858

5959
<dd><a
60-
href="http://www.w3.org/TR/2012/ED-css3-regions-20121019/">http://www.w3.org/csswg/css3-regions</a>
60+
href="http://www.w3.org/TR/2012/ED-css3-regions-20121105/">http://www.w3.org/csswg/css3-regions</a>
6161

6262
<dt>Latest version:
6363

@@ -564,17 +564,6 @@ <h2 id=css-regions-concepts><span class=secno>2. </span>CSS regions
564564

565565
<h3 id=regions><span class=secno>2.1. </span>Regions</h3>
566566

567-
<div class="issue-marker wrapper">
568-
<div class=issue-marker data-bug_id=15186 data-bug_status=NEW> <a
569-
href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=15186">Issue-15186</a>
570-
571-
<div class=issue-details>
572-
<p class=short-desc>Is a mechanism to auto-generate regions necessary in
573-
order to support reusable style sheets?
574-
</div>
575-
</div>
576-
</div>
577-
578567
<p id=region> A <dfn id=css-region title=region>CSS Region</dfn> is a block
579568
container that has an associated <a href="#named-flow0"><em><span>named
580569
flow</span></em></a> (see the ‘<a href="#flow-from"><code
@@ -961,14 +950,6 @@ <h3 id=the-flow-from-property><span class=secno>3.2. </span>The ‘<a
961950
</div>
962951

963952
<div class="issue-marker wrapper">
964-
<div class=issue-marker data-bug_id=15824 data-bug_status=NEW> <a
965-
href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=15824">Issue-15824</a>
966-
967-
<div class=issue-details>
968-
<p class=short-desc>Should regions not create a new stacking context?
969-
</div>
970-
</div>
971-
972953
<div class=issue-marker data-bug_id=15827 data-bug_status=NEW> <a
973954
href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=15824">Issue-15827</a>
974955

@@ -2220,7 +2201,7 @@ <h3 id=region-flow-layout-events><span class=secno>6.4. </span>Region flow
22202201
<p><a href="#dom-named-flow"><code class=idl>NamedFlow</code></a> objects
22212202
are <a
22222203
href="http://www.w3.org/TR/dom/#interface-eventtarget">EventTargets</a>
2223-
which dispatch <code class=idl>regionLayoutUpdate</code> events when there
2204+
which dispatch <code class=idl>regionlayoutupdate</code> events when there
22242205
is a possible layout change in their region chain. The event is
22252206
asynchronous, and fires in the same step of the <a
22262207
href="http://www.w3.org/TR/html5/webappapis.html#processing-model-2">event
@@ -2233,8 +2214,8 @@ <h3 id=region-flow-layout-events><span class=secno>6.4. </span>Region flow
22332214
href="#dom-named-flow"><code class=idl>NamedFlow</code></a> contains
22342215
regions for a different <a href="#dom-named-flow"><code
22352216
class=idl>NamedFlow</code></a>) then the <code
2236-
class=idl>regionLayoutUpdate</code> event for the nested flow(s) must be
2237-
dispatched before the <code class=idl>regionLayoutUpdate</code> event for
2217+
class=idl>regionlayoutupdate</code> event for the nested flow(s) must be
2218+
dispatched before the <code class=idl>regionlayoutupdate</code> event for
22382219
the containing flow is dispatched.
22392220

22402221
<table border=0 cellpadding=2 cellspacing=0 class=event-desc
@@ -2243,7 +2224,7 @@ <h3 id=region-flow-layout-events><span class=secno>6.4. </span>Region flow
22432224
<tr class="assert must">
22442225
<th>Type
22452226

2246-
<td class=eventname><strong><code>regionLayoutUpdate</code></strong>
2227+
<td class=eventname><strong><code>regionlayoutupdate</code></strong>
22472228

22482229
<tr class="assert must">
22492230
<th>Interface
@@ -2803,6 +2784,10 @@ <h3 id="changes_from_Aug_28_2012"><span class=secno>12.1. </span>Changes
28032784
28<sup>th</sup> 2012</a> version</h3>
28042785

28052786
<ul>
2787+
<li>Changed case of regionlayoutupdate to match other events in <a
2788+
href="#DOM-LEVEL-3-EVENTS"
2789+
rel=biblioentry>[DOM-LEVEL-3-EVENTS]<!--{{DOM-LEVEL-3-EVENTS}}--></a>
2790+
28062791
<li>Added section on fragmenting the fragmenters
28072792

28082793
<li>Added section on handling circular flow-from and flow-into situations

‎css3-regions/Overview.src.html‎

Lines changed: 5 additions & 25 deletions
Original file line numberDiff line numberDiff line change
@@ -326,18 +326,6 @@ <h2 id="css-regions-concepts">CSS regions concepts</h2>
326326

327327
<h3 id="regions">Regions</h3>
328328

329-
<div class="issue-marker wrapper">
330-
<div class="issue-marker" data-bug_id="15186" data-bug_status="NEW">
331-
<a href=
332-
"https://www.w3.org/Bugs/Public/show_bug.cgi?id=15186">Issue-15186</a>
333-
334-
<div class="issue-details">
335-
<p class="short-desc">Is a mechanism to auto-generate regions
336-
necessary in order to support reusable style sheets?</p>
337-
</div>
338-
</div>
339-
</div>
340-
341329
<p id="region">
342330
A <dfn title="region">CSS Region</dfn>
343331
is a block container
@@ -782,15 +770,6 @@ <h3 id="the-flow-from-property">The 'flow-from' property</h3>
782770
</div>
783771

784772
<div class="issue-marker wrapper">
785-
<div class="issue-marker" data-bug_id="15824" data-bug_status="NEW">
786-
787-
<a href=
788-
"https://www.w3.org/Bugs/Public/show_bug.cgi?id=15824">Issue-15824</a>
789-
790-
<div class="issue-details">
791-
<p class="short-desc">Should regions not create a new stacking context?</p>
792-
</div>
793-
</div>
794773
<div class="issue-marker" data-bug_id="15827" data-bug_status="NEW">
795774

796775
<a href=
@@ -1998,7 +1977,7 @@ <h3 id="region-flow-layout-events">Region flow layout events</h3>
19981977

19991978
<p><a href="#dom-named-flow"><code class="idl">NamedFlow</code></a>
20001979
objects are <a href="http://www.w3.org/TR/dom/#interface-eventtarget">EventTargets</a>
2001-
which dispatch <code class="idl">regionLayoutUpdate</code> events
1980+
which dispatch <code class="idl">regionlayoutupdate</code> events
20021981
when there is a possible layout change
20031982
in their region chain.
20041983
The event is asynchronous,
@@ -2011,16 +1990,16 @@ <h3 id="region-flow-layout-events">Region flow layout events</h3>
20111990
(the contents of a <a href="#dom-named-flow"><code class="idl">NamedFlow</code></a>
20121991
contains regions
20131992
for a different <a href="#dom-named-flow"><code class="idl">NamedFlow</code></a>)
2014-
then the <code class="idl">regionLayoutUpdate</code> event
1993+
then the <code class="idl">regionlayoutupdate</code> event
20151994
for the nested flow(s)
20161995
must be dispatched
2017-
before the <code class="idl">regionLayoutUpdate</code> event
1996+
before the <code class="idl">regionlayoutupdate</code> event
20181997
for the containing flow
20191998
is dispatched.</p>
20201999

20212000
<table class="event-desc" border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0">
20222001
<tbody><tr class="assert must"><th>Type</th>
2023-
<td class="eventname"><strong><code>regionLayoutUpdate</code></strong></td></tr>
2002+
<td class="eventname"><strong><code>regionlayoutupdate</code></strong></td></tr>
20242003
<tr class="assert must"><th>Interface</th> <td><code><a href="http://www.w3.org/TR/DOM-Level-3-Events/#events-UIEvent">UIEvent</a></code> (see [[!DOM-LEVEL-3-EVENTS]])</td></tr>
20252004
<tr class="assert must"><th>Sync / Async</th> <td>Async</td></tr>
20262005
<tr class="assert must"><th>Bubbles</th> <td>No</td></tr>
@@ -2442,6 +2421,7 @@ <h2 id="changes">Changes</h2>
24422421
<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>
24432422

24442423
<ul>
2424+
<li>Changed case of regionlayoutupdate to match other events in [[DOM-LEVEL-3-EVENTS]]</li>
24452425
<li>Added section on fragmenting the fragmenters</li>
24462426
<li>Added section on handling circular flow-from and flow-into situations</li>
24472427
<li>Added alignment and justification to region styling properties</li>

0 commit comments

Comments
 (0)