@@ -955,7 +955,7 @@ <h2 class="heading settled" data-level="6" id="fragment-overflow"><span class="s
955955 < p class ="issue " id ="issue-89a60b9c "> < a class ="self-link " href ="#issue-89a60b9c "> </ a >
956956 What if we want to be able to style the pieces of an element
957957 split within another type of fragmentation context?
958- These rules prevent ever using < span class ="css "> ::nth-fragment()</ span > for that,
958+ These rules prevent ever using < a class ="css " data-link-type =" maybe " href =" #selectordef-nth-fragment " > ::nth-fragment()</ a > for that,
959959 despite that the name seems the most logical name for such a feature.
960960 </ p >
961961
@@ -1046,7 +1046,8 @@ <h4 class="heading settled" data-level="6.1.1" id="fragment-pseudo-element"><spa
10461046
10471047
10481048 < p >
1049- The ::nth-fragment() pseudo-element is a pseudo-element
1049+ The < dfn class ="css " data-dfn-type ="selector " data-export ="" id ="selectordef-nth-fragment "> ::nth-fragment()< a class ="self-link " href ="#selectordef-nth-fragment "> </ a > </ dfn > pseudo-element
1050+ is a pseudo-element
10501051 that describes some of the < a data-link-type ="dfn " href ="#fragment-box "> fragment box</ a > es generated by an element.
10511052 The argument to the pseudo-element takes the same syntax
10521053 as the argument to the :nth-child() pseudo-class
@@ -1087,16 +1088,16 @@ <h4 class="heading settled" data-level="6.1.2" id="style-of-fragments"><span cla
10871088
10881089
10891090 < p >
1090- In the absence of rules with < span class ="css "> ::nth-fragment()</ span > pseudo-elements,
1091+ In the absence of rules with < a class ="css " data-link-type =" maybe " href =" #selectordef-nth-fragment " > ::nth-fragment()</ a > pseudo-elements,
10911092 the computed style for each < a data-link-type ="dfn " href ="#fragment-box "> fragment box</ a >
10921093 is the computed style for the element
10931094 for which the < a data-link-type ="dfn " href ="#fragment-box "> fragment box</ a > was created.
10941095 However, the style for a < a data-link-type ="dfn " href ="#fragment-box "> fragment box</ a > is also influenced
10951096 by rules whose selector’s < a data-link-type ="dfn " href ="http://dev.w3.org/csswg/selectors-3/#subject "> subject</ a > < a data-link-type ="biblio " href ="#biblio-select "> [SELECT]</ a >
1096- has an < span class ="css "> ::nth-fragment()</ span > pseudo-element,
1097+ has an < a class ="css " data-link-type =" maybe " href =" #selectordef-nth-fragment " > ::nth-fragment()</ a > pseudo-element,
10971098 if the 1-based number of the < a data-link-type ="dfn " href ="#fragment-box "> fragment box</ a > matches
1098- that < span class ="css "> ::nth-fragment()</ span > pseudo-element
1099- and the selector (excluding the < span class ="css "> ::nth-fragment()</ span > pseudo-element)
1099+ that < a class ="css " data-link-type =" maybe " href =" #selectordef-nth-fragment " > ::nth-fragment()</ a > pseudo-element
1100+ and the selector (excluding the < a class ="css " data-link-type =" maybe " href =" #selectordef-nth-fragment " > ::nth-fragment()</ a > pseudo-element)
11001101 matches the element generating the fragments.
11011102 </ p >
11021103
@@ -1159,7 +1160,7 @@ <h4 class="heading settled" data-level="6.1.2" id="style-of-fragments"><span cla
11591160
11601161
11611162 < p >
1162- Styling an < span class ="css "> ::nth-fragment()</ span > pseudo-element with the < a class ="property " data-link-type ="propdesc " href ="#propdef-overflow "> overflow</ a >
1163+ Styling an < a class ="css " data-link-type =" maybe " href =" #selectordef-nth-fragment " > ::nth-fragment()</ a > pseudo-element with the < a class ="property " data-link-type ="propdesc " href ="#propdef-overflow "> overflow</ a >
11631164 property does take effect;
11641165 if a < a data-link-type ="dfn " href ="#fragment-box "> fragment box</ a > has a
11651166 computed value of < a class ="property " data-link-type ="propdesc " href ="#propdef-overflow "> overflow</ a > other than < a class ="css " data-link-type ="maybe " href ="#valdef-overflow-fragments "> fragments</ a >
@@ -1176,7 +1177,7 @@ <h4 class="heading settled" data-level="6.1.2" id="style-of-fragments"><span cla
11761177
11771178
11781179 < p >
1179- Styling an < span class ="css "> ::nth-fragment()</ span > pseudo-element with the < a class ="property " data-link-type ="propdesc " href ="http://dev.w3.org/csswg/css-content-3/#propdef-content "> content</ a >
1180+ Styling an < a class ="css " data-link-type =" maybe " href =" #selectordef-nth-fragment " > ::nth-fragment()</ a > pseudo-element with the < a class ="property " data-link-type ="propdesc " href ="http://dev.w3.org/csswg/css-content-3/#propdef-content "> content</ a >
11801181 property has no effect;
11811182 the computed value of < a class ="property " data-link-type ="propdesc " href ="http://dev.w3.org/csswg/css-content-3/#propdef-content "> content</ a > for the fragment box
11821183 remains the same as the computed value of content for the element.
@@ -1187,7 +1188,7 @@ <h4 class="heading settled" data-level="6.1.2" id="style-of-fragments"><span cla
11871188 Specifying < a class ="css " data-link-type ="propdesc " href ="http://dev.w3.org/csswg/css2/visuren.html#propdef-display "> display: none</ a > for a < a data-link-type ="dfn " href ="#fragment-box "> fragment box</ a > causes
11881189 the fragment box with that index not to be generated.
11891190 However, in terms of the indices
1190- used for matching < span class ="css "> ::nth-fragment()</ span > pseudo-elements
1191+ used for matching < a class ="css " data-link-type =" maybe " href =" #selectordef-nth-fragment " > ::nth-fragment()</ a > pseudo-elements
11911192 of later fragment boxes,
11921193 it still counts as though it was generated.
11931194 However, since it is not generated, it does not contain any content.
@@ -1212,15 +1213,15 @@ <h4 class="heading settled" data-level="6.1.2" id="style-of-fragments"><span cla
12121213 < p >
12131214 To match the model for other pseudo-elements
12141215 where the pseudo-elements live inside their corresponding element,
1215- declarations in < span class ="css "> ::nth-fragment()</ span > pseudo-elements override
1216+ declarations in < a class ="css " data-link-type =" maybe " href =" #selectordef-nth-fragment " > ::nth-fragment()</ a > pseudo-elements override
12161217 declarations in rules without the pseudo-element.
12171218 The relative priority within such declarations is determined
12181219 by normal cascading order (see < a data-link-type ="biblio " href ="#biblio-css21 "> [CSS21]</ a > ).
12191220 </ p >
12201221
12211222
12221223 < p >
1223- Styles specified on < span class ="css "> ::nth-fragment()</ span > pseudo-elements
1224+ Styles specified on < a class ="css " data-link-type =" maybe " href =" #selectordef-nth-fragment " > ::nth-fragment()</ a > pseudo-elements
12241225 do affect inheritance to content within the < a data-link-type ="dfn " href ="#fragment-box "> fragment box</ a > .
12251226 In other words, the content within the < a data-link-type ="dfn " href ="#fragment-box "> fragment box</ a > must
12261227 inherit from the fragment box’s style (i.e., the pseudo-element style)
@@ -1291,11 +1292,11 @@ <h4 class="heading settled" data-level="6.1.3" id="style-in-fragments"><span cla
12911292
12921293
12931294 < p >
1294- The < span class ="css "> ::nth-fragment()</ span > pseudo-element
1295+ The < a class ="css " data-link-type =" maybe " href =" #selectordef-nth-fragment " > ::nth-fragment()</ a > pseudo-element
12951296 can also be used to style
12961297 content inside of a < a data-link-type ="dfn " href ="#fragment-box "> fragment box</ a > .
12971298 Unlike the < a class ="css " data-link-type ="maybe " href ="http://dev.w3.org/csswg/css-pseudo-4/#selectordef-first-line "> ::first-line</ a > and < span class ="css "> ::first-letter</ span > pseudo-elements,
1298- the < span class ="css "> ::nth-fragment()</ span > pseudo-element can be applied
1299+ the < a class ="css " data-link-type =" maybe " href =" #selectordef-nth-fragment " > ::nth-fragment()</ a > pseudo-element can be applied
12991300 to parts of the selector other than the subject:
13001301 in particular, it can match ancestors of the subject.
13011302 However, the only CSS properties applied
@@ -1307,7 +1308,7 @@ <h4 class="heading settled" data-level="6.1.3" id="style-in-fragments"><span cla
13071308
13081309 < p >
13091310 To be more precise,
1310- when a rule’s selector has < span class ="css "> ::nth-fragment()</ span > pseudo-elements
1311+ when a rule’s selector has < a class ="css " data-link-type =" maybe " href =" #selectordef-nth-fragment " > ::nth-fragment()</ a > pseudo-elements
13111312 attached to parts of the selector other than the subject,
13121313 the declarations in that rule apply to
13131314 a fragment (or pseudo-element thereof) when:
@@ -1324,15 +1325,15 @@ <h4 class="heading settled" data-level="6.1.3" id="style-in-fragments"><span cla
13241325 < li >
13251326 the declarations would apply to
13261327 that fragment (or pseudo-element thereof)
1327- had those < span class ="css "> ::nth-fragment()</ span > pseudo-elements been removed,
1328+ had those < a class ="css " data-link-type =" maybe " href =" #selectordef-nth-fragment " > ::nth-fragment()</ a > pseudo-elements been removed,
13281329 with a particular association between
13291330 each sequence of simple selectors and the element it matched,
13301331 and
13311332
13321333
13331334
13341335 < li >
1335- for each removed < span class ="css "> ::nth-fragment()</ span > pseudo-element,
1336+ for each removed < a class ="css " data-link-type =" maybe " href =" #selectordef-nth-fragment " > ::nth-fragment()</ a > pseudo-element,
13361337 the fragment lives within a < a data-link-type ="dfn " href ="#fragment-box "> fragment box</ a >
13371338 of the element associated in that association
13381339 with the selector that the pseudo-element was attached to,
@@ -1811,6 +1812,7 @@ <h2 class="no-num heading settled" id="index"><span class="content">Index</span>
18111812 < li > max-lines, < a href ="#propdef-max-lines "> 6.2</ a >
18121813 < li > non-3d-preserving child, < a href ="#non_3d_preserving-child "> 2.2</ a >
18131814 < li > none, < a href ="#valdef-max-lines-none "> 6.2</ a >
1815+ < li > ::nth-fragment(), < a href ="#selectordef-nth-fragment "> 6.1.1</ a >
18141816 < li > overflow
18151817 < ul >
18161818 < li > definition of, < a href ="#overflow "> 2</ a >
@@ -1982,7 +1984,7 @@ <h2 class="no-num heading settled" id="issues-index"><span class="content">Issue
19821984 < div class ="issue ">
19831985 What if we want to be able to style the pieces of an element
19841986 split within another type of fragmentation context?
1985- These rules prevent ever using < span class ="css "> ::nth-fragment()</ span > for that,
1987+ These rules prevent ever using < a class ="css " data-link-type =" maybe " href =" #selectordef-nth-fragment " > ::nth-fragment()</ a > for that,
19861988 despite that the name seems the most logical name for such a feature.
19871989 < a href ="#issue-89a60b9c "> ↵ </ a > </ div >
19881990 < div class ="issue ">
0 commit comments