@@ -103,7 +103,7 @@ Request URL Modifiers</h4>
103
103
</dl>
104
104
105
105
<div algorithm>
106
- To <dfn>apply request modifiers from URL value</dfn>
106
+ To <dfn export >apply request modifiers from URL value</dfn>
107
107
given a [=/request=] |req|
108
108
and a <<url>> |url|,
109
109
call the [=request modifier steps=] for |url|'s <<request-url-modifier>> s in sequence
@@ -133,7 +133,7 @@ Interpolation Progress Functional Notations</h2>
133
133
such as a [=math function=]
134
134
or a [=mix notation=] .
135
135
136
- <h3 id="progress">
136
+ <h3 id="progress-func ">
137
137
Calculated Progress Values: the ''progress()'' notation</h3>
138
138
139
139
The <dfn>progress()</dfn> functional notation
@@ -150,7 +150,7 @@ Calculated Progress Values: the ''progress()'' notation</h3>
150
150
The syntax of ''progress()'' is defined as follows:
151
151
152
152
<pre class=prod>
153
- <dfn><<progress()>></dfn> = progress(<<calc-sum>> from <<calc-sum>> to <<calc-sum>> )
153
+ <dfn id=typedef-progress-fn ><<progress()>></dfn> = progress(<<calc-sum>> from <<calc-sum>> to <<calc-sum>> )
154
154
</pre>
155
155
156
156
where the first, second, and third <<calc-sum>> values represent
@@ -167,7 +167,7 @@ Calculated Progress Values: the ''progress()'' notation</h3>
167
167
Note: The ''progress()'' function is essentially syntactic sugar
168
168
for a particular pattern of ''calc()'' notations.
169
169
170
- <h3 id="progress">
170
+ <h3 id="media- progress-func ">
171
171
Media Query Progress Values: the ''media-progress()'' notation</h3>
172
172
173
173
Similar to the ''progress()'' notation,
@@ -194,7 +194,7 @@ Media Query Progress Values: the ''media-progress()'' notation</h3>
194
194
must be valid values for the specified [=media query=] ,
195
195
or else the function is invalid.
196
196
197
- <h3 id="progress">
197
+ <h3 id="container- progress-func ">
198
198
Container Query Progress Values: the ''container-progress()'' notation</h3>
199
199
200
200
The <dfn>container-progress()</dfn> functional notation
@@ -228,7 +228,7 @@ Mixing and Interpolation Notations: the *-mix() family</h2>
228
228
These [=functional notations=] follow the syntactic pattern:
229
229
230
230
<pre class=prod>
231
- <var>mix-function</var>() = <var>mix-function</var>( <<progress>> , << start-value>> , << end-value>> )
231
+ <var>mix-function</var>() = <var>mix-function</var>( <<progress>> , [=mix start value|start -value=], [=mix end value|end -value=] )
232
232
</pre>
233
233
234
234
The [=mix notations=] in CSS include:
@@ -256,7 +256,7 @@ Mixing and Interpolation Notations: the *-mix() family</h2>
256
256
but how would we represent a set of keyframes for a [=component value=]
257
257
(rather than a full property value)?
258
258
259
- <h3 id="progress">
259
+ <h3 id="progress-type ">
260
260
Representing Interpolation Progress: the <<progress>> type</h2>
261
261
262
262
The <dfn><<progress>></dfn> value type represents
@@ -347,7 +347,7 @@ Interpolated Numeric and Dimensional Values: the ''color-mix()'' notation</h3>
347
347
<pre class=prod>
348
348
<<color-mix()>> =
349
349
color-mix( <<progress>> && <<color-interpolation-method>> ?, <<color>> , <<color>> ) |
350
- color-mix( <<color-interpolation-method>> , [<<color>> && <<percentage[0,100]>> ?]#{2} )
350
+ color-mix( <<color-interpolation-method>> , [<<color>> && <<percentage [0,100]>> ?]#{2} )
351
351
</pre>
352
352
353
353
The used value of the first [=mix notation=] variant
@@ -632,12 +632,18 @@ Ian's proposal:
632
632
substitutes a [=custom property=] value into a function.
633
633
634
634
<pre class=prod>
635
- attr() = attr( <<q-name>> <<attr-type>> ? , <<declaration-value>> ?)
635
+ attr() = attr( <<attr-name>> <<attr-type>> ? , <<declaration-value>> ?)
636
+
637
+ <dfn><attr-name></dfn> = [ <<ident-token>> '|' ]? <<ident-token>>
636
638
637
639
<dfn><attr-type></dfn> = string | url | ident | color | number | percentage |
638
640
length | angle | time | frequency | flex | <<dimension-unit>>
639
641
</pre>
640
642
643
+ <!-- Switch the <attr-name> to just use <q-name>
644
+ when Namespaces is rewritten
645
+ to use the current grammar structures. -->
646
+
641
647
The <dfn><dimension-unit></dfn> production matches a literal "%" character
642
648
(that is, a <<delim-token>> with a value of "%")
643
649
or an ident whose value is any of the CSS units
@@ -646,8 +652,10 @@ Ian's proposal:
646
652
647
653
The arguments of ''attr()'' are:
648
654
649
- : <<q-name>>
650
- :: Gives the name of the attribute being referenced.
655
+ : <<attr-name>>
656
+ :: Gives the name of the attribute being referenced,
657
+ similar to <<wq-name>> (from [[SELECTORS-3]] )
658
+ but without the possibility of a wildcard prefix.
651
659
652
660
If no namespace is specified
653
661
(just an identifier is given, like ''attr(foo)'' ),
@@ -656,7 +664,7 @@ Ian's proposal:
656
664
as namespaced attributes are rare.
657
665
In particular, HTML and SVG do not contain namespaced attributes.)
658
666
As with [=attribute selectors=] ,
659
- the case-sensitivity of <<q -name>> depends on the document language.
667
+ the case-sensitivity of <<attr -name>> depends on the document language.
660
668
661
669
If ''attr()'' is used in a property applied to an element,
662
670
it references the attribute of the given name on that element;
@@ -1243,7 +1251,7 @@ Generating/Caching Random Values: the <<random-caching-options>> value</h4>
1243
1251
}
1244
1252
</pre>
1245
1253
1246
- But so long as the [=used- values=] end up identical,
1254
+ But so long as the [=used values=] end up identical,
1247
1255
two functions that look distinct might end up identical.
1248
1256
For example, in the following code:
1249
1257
0 commit comments