Skip to content

Commit e4fbebd

Browse files
committed
Fix places where I was short one colon.
1 parent ca50889 commit e4fbebd

2 files changed

Lines changed: 12 additions & 12 deletions

File tree

css3-overflow/Overview.html

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -293,10 +293,10 @@ <h2 id=region-overflow><span class=secno>3. </span>Region overflow</h2>
293293
columns or pages; the pieces that are in separate columns or pages are
294294
always distinct region boxes.)
295295

296-
<p class=issue> We also want ‘<code class=css>:nth-region()</code>
296+
<p class=issue> We also want ‘<code class=css>::nth-region()</code>
297297
pseudo-elements to be able to apply to the pieces of an element split
298298
within a fragmentation context. Should we require that authors who want to
299-
use ‘<code class=css>:nth-region()</code>’ in this way specify
299+
use ‘<code class=css>::nth-region()</code>’ in this way specify
300300
<code class=css>overflow:regions</code>’ (even if they don't specify
301301
a constrained height), or should it work automatically for all elements
302302
even if they don't have ‘<code class=css>overflow: regions</code>’?
@@ -394,7 +394,7 @@ <h4 id=style-of-regions><span class=secno>3.1.2. </span>Styling of regions</h4>
394394
(excluding the ‘<code class=css>::nth-region()</code>’ pseudo-element)
395395
matches the element generating the regions.
396396

397-
<p> Styling an ‘<code class=css>:nth-region()</code>’ pseudo-element
397+
<p> Styling an ‘<code class=css>::nth-region()</code>’ pseudo-element
398398
with the ‘<code class=property>overflow</code>’ property has no
399399
effect; the computed value of ‘<code class=property>overflow</code>
400400
for the region box remains the same as the computed value of overflow for
@@ -403,7 +403,7 @@ <h4 id=style-of-regions><span class=secno>3.1.2. </span>Styling of regions</h4>
403403
<p> Specifying ‘<code class=css>display: none</code>’ for a region box
404404
causes the region box with that index not to be generated. However, in
405405
terms of the indices used for matching ‘<code
406-
class=css>:nth-region()</code>’ pseudo-elements of later region boxes,
406+
class=css>::nth-region()</code>’ pseudo-elements of later region boxes,
407407
it still counts as though it was generated. However, since it is not
408408
generated, it does not contain any content.
409409

@@ -443,11 +443,11 @@ <h4 id=style-in-regions><span class=secno>3.1.3. </span>Styling inside
443443
<p class=issue> Should this apply to region overflow only, or also to
444444
paginated overflow, or even to pagination across pages?
445445

446-
<p> The ‘<code class=css>:nth-region()</code>’ pseudo-element can also
446+
<p> The ‘<code class=css>::nth-region()</code>’ pseudo-element can also
447447
be used to style content inside of a <a href="#region-box"><i>region
448448
box</i></a>. Unlike the ‘<code class=css>::first-line</code>’ and
449449
<code class=css>::first-letter</code>’ pseudo-elements, the ‘<code
450-
class=css>:nth-region()</code>’ pseudo-element can be applied to parts
450+
class=css>::nth-region()</code>’ pseudo-element can be applied to parts
451451
of the selector other than the subject: in particular, it can match
452452
ancestors of the subject. However, the only CSS properties applied by
453453
rules with such selectors are those that apply to the ‘<code

css3-overflow/Overview.src.html

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -198,11 +198,11 @@ <h2 id="region-overflow">Region overflow</h2>
198198
</p>
199199

200200
<p class="issue">
201-
We also want '':nth-region()'' pseudo-elements
201+
We also want ''::nth-region()'' pseudo-elements
202202
to be able to apply to the pieces of an element
203203
split within a fragmentation context.
204204
Should we require that authors who want to use
205-
'':nth-region()'' in this way specify ''overflow:regions''
205+
''::nth-region()'' in this way specify ''overflow:regions''
206206
(even if they don't specify a constrained height),
207207
or should it work automatically for all elements
208208
even if they don't have ''overflow: regions''?
@@ -299,7 +299,7 @@ <h4 id="style-of-regions">Styling of regions</h4>
299299
</p>
300300

301301
<p>
302-
Styling an '':nth-region()'' pseudo-element with the 'overflow'
302+
Styling an ''::nth-region()'' pseudo-element with the 'overflow'
303303
property has no effect;
304304
the computed value of 'overflow' for the region box
305305
remains the same as the computed value of overflow for the element.
@@ -309,7 +309,7 @@ <h4 id="style-of-regions">Styling of regions</h4>
309309
Specifying ''display: none'' for a region box causes
310310
the region box with that index not to be generated.
311311
However, in terms of the indices
312-
used for matching '':nth-region()'' pseudo-elements
312+
used for matching ''::nth-region()'' pseudo-elements
313313
of later region boxes,
314314
it still counts as though it was generated.
315315
However, since it is not generated, it does not contain any content.
@@ -360,11 +360,11 @@ <h4 id="style-in-regions">Styling inside regions</h4>
360360
</p>
361361

362362
<p>
363-
The '':nth-region()'' pseudo-element
363+
The ''::nth-region()'' pseudo-element
364364
can also be used to style
365365
content inside of a <i>region box</i>.
366366
Unlike the ''::first-line'' and ''::first-letter'' pseudo-elements,
367-
the '':nth-region()'' pseudo-element can be applied
367+
the ''::nth-region()'' pseudo-element can be applied
368368
to parts of the selector other than the subject:
369369
in particular, it can match ancestors of the subject.
370370
However, the only CSS properties applied

0 commit comments

Comments
 (0)