-
Notifications
You must be signed in to change notification settings - Fork 790
Expand file tree
/
Copy pathcascade.src
More file actions
510 lines (403 loc) · 19.2 KB
/
cascade.src
File metadata and controls
510 lines (403 loc) · 19.2 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
<html lang="en">
<!-- $Id: cascade.src,v 2.78 2012-08-21 13:50:54 bbos Exp $ -->
<HEAD>
<TITLE>Assigning property values, Cascading, and Inheritance</TITLE>
<!--script src="http://www.w3c-test.org/css/harness/annotate.js#CSS21_DEV" type="text/javascript" defer></script-->
</HEAD>
<BODY>
<h1>Assigning property values, Cascading, and Inheritance</h1>
<h2><a name="value-stages">Specified, computed, and actual values</a></h2>
<p>Once a user agent has parsed a document and constructed a <a
href="conform.html#doctree">document tree</a>, it must assign, for
every element in the tree, a value to every property that applies to the
target <a href="media.html">media type</a>.
<p>The final value of a property is the result of a four-step
calculation: the value is determined through specification (the
"specified value"), then resolved into a value that is used for
inheritance (the "computed value"), then converted into an absolute
value if necessary (the "used value"), and finally transformed
according to the limitations of the local environment (the "actual
value").
<h3><span class="index-def" title="specified value">
<a name="specified-value">Specified values</a></span></h3>
<p>User agents must first assign a specified value to each property based
on the following mechanisms (in order of precedence):</p>
<ol>
<li>If the <a href="#cascade">cascade</a> results in a value, use it.
Except that, if the value is 'inherit', the specified value is defined
in <a href="#value-def-inherit" >“The 'inherit' value”</a> below.
<li>Otherwise, if the property is <a href="#inheritance">inherited</a> and the element is not the root of the <a>document tree</a>, use the computed value of the parent element.
<li>Otherwise use the property's <span class="index-def" title="initial value">initial value</span>. The initial value of each property is indicated in the property's definition.
</ol>
<h3><span class="index-def" title="computed value">
<a name="computed-value">Computed values</a></span></h3>
<p>Specified values are resolved to computed values during the cascade;
for example URIs are made absolute and 'em' and 'ex'
units are computed to pixel or absolute lengths. Computing a value
never requires the user agent to render the document.
<p>The computed value of URIs that the UA cannot resolve to absolute
URIs is the specified value.
<p>The computed value of a
property is determined as specified by the Computed Value line in the
definition of the
property. See the section on <a href="#inheritance">inheritance</a>
for the definition of computed values when the specified value is
'inherit'.
<p>The computed value exists even when the property does not apply, as
defined by the <a href="about.html#applies-to">'Applies To'</a> line.
However, some
properties may define the computed value of a property for an element
to depend on whether the property applies to that element.
<h3><span class="index-def" title="used value">
<a name="used-value">Used values</a></span></h3>
<p>Computed values are processed as far as possible without formatting
the document. Some values, however, can only be determined when the
document is being laid out. For example, if the width of an element is
set to be a certain percentage of its containing block, the width
cannot be determined until the width of the containing block has been
determined. The <dfn id="usedValue">used value</dfn> is the result of
taking the computed value and resolving any remaining dependencies
into an absolute value.
<h3><span class="index-def" title="actual value">
<a name="actual-value">Actual values</a></span></h3>
<p>A used value is in principle the value used for rendering, but a
user agent may not be able to make use of the value in a given
environment. For example, a user agent may only be able to render
borders with integer pixel widths and may therefore have to
approximate the computed width, or the user agent may be forced to
use only black and white shades instead of full color. The actual
value is the used value after any approximations have been applied.
<h2><a name="inheritance">Inheritance</a></h2>
<p>Some values are inherited by the children of an element in the <a
href="conform.html#doctree">document tree</a>, as described <a
href="#specified-value">above</a>. Each property <a
href="about.html#property-defs">defines</a> whether it is inherited or
not.
<div class="html-example"><P>
Suppose there is an H1 element with an emphasizing element (EM)
inside:</p>
<pre>
<H1>The headline <EM>is</EM> important!</H1>
</pre>
<p>If no color has been assigned to the EM element, the emphasized
"is" will inherit the color of the parent element, so if H1 has the
color blue, the EM element will likewise be in blue.
</div>
<p>When inheritance occurs, elements inherit computed values. The
computed value from the parent element becomes both the specified
value and the computed value on the child.
<div class="example"><P>
For example, given the following style sheet:</P>
<pre>
body { font-size: 10pt }
h1 { font-size: 130% }
</pre>
<p>and this document fragment:
<pre class="html-example">
<BODY>
<H1>A <EM>large</EM> heading</H1>
</BODY>
</pre>
<p>the <span class="prop-inst-font-size">'font-size'</span> property
for the H1 element will have the computed value '13pt' (130% times
10pt, the parent's value). Since the computed value of <span
class="propinst-font-size">'font-size'</span> is inherited, the EM
element will have the computed value '13pt' as well. If the
user agent does not have the 13pt font available, the
actual value of <span class="propinst-font-size">'font-size'</span>
for both H1 and EM might be, for example, '12pt'.
</div>
<p class=note>Note that inheritance follows the document tree and is
not intercepted by <span class=index-inst><a
href="visuren.html#box-gen">anonymous boxes.</a></span>
<h3>The <span class="index-def" title="inherit, definition
of"><a name="value-def-inherit">'inherit'</a></span>
value</h3>
<P>Each property may also have a cascaded value of 'inherit', which
means that, for a given element, the property takes as specified
value the computed value of the element's parent. The 'inherit' value
can be used to enforce inheritance of values, and it can also be used on
properties that are not normally inherited.
<p>If the 'inherit' value is set on the root element, the property is
assigned its initial value.
<div class="example"><P>In the example below, the <span
class="propinst-color">'color'</span> and <span
class="propinst-background">'background'</span> properties are set on
the BODY element. On all other elements, the 'color' value will be
inherited and the background will be transparent. If these rules are
part of the user's style sheet, black text on a white background will
be enforced throughout the document.
<PRE>
body {
color: black !important;
background: white !important;
}
* {
color: inherit !important;
background: transparent !important;
}
</PRE>
</div>
<!-- Add another example?. Check out:
http://lists.w3.org/Archives/Member/w3c-css-wg/1998JanMar/0054.html
-IJ, HWL -->
<H2><a name="at-import">The @import rule</a></h2>
<P>The <span class="index-def"
title="@import"><dfn>'@import'</dfn></span> rule allows users to
import style rules from other style sheets. In CSS 2.1, any
@import rules must precede all other rules (except the @charset rule,
if present). See the <a href="syndata.html#at-rules">section on
parsing</a> for when user agents must ignore @import rules. The
'@import' keyword must be followed by the URI of the style sheet to
include. A string is also allowed; it will be interpreted as if it had
url(...) around it.
<div class="example"><P>
The following lines are equivalent in meaning and illustrate both
'@import' syntaxes (one with "url()" and one with a bare string):</p>
<PRE>
@import "mystyle.css";
@import url("mystyle.css");
</PRE>
</div>
<p>So that user agents can avoid retrieving resources for unsupported
<a href="media.html">media types</a>, authors may specify
media-dependent <span class="index-inst"
title="@import">@import</span> rules. These <span class="index-def"
title="conditional import|media-dependent import">conditional
imports</span> specify comma-separated media types after the URI.
<div class="example">
<p>The following rules illustrate how @import rules can be made media-dependent:</p>
<pre>
@import url("fineprint.css") print;
@import url("bluish.css") projection, tv;
</pre>
</div>
<p>In the absence of any media types, the import is
unconditional. Specifying 'all' for the medium has the same effect.
The import only takes effect if the target medium matches the media
list.
<p>A target medium matches a media list if one of the items in the
media list is the target medium or 'all'.
<p class=note>Note that Media Queries [[MEDIAQ]] extends the syntax of
media lists and the definition of matching.
<p>When the same style sheet is imported or linked to a document in
multiple places, user agents must process (or act as though they do)
each link as though the link were to a separate style sheet.
<H2><a name="cascade">The cascade</a></h2>
<P>Style sheets may have three different origins: author, user, and
user agent.</p>
<ul>
<li><strong>Author</strong>. The author specifies style sheets
for a source document according to the conventions of the document
language. For instance, in HTML, style sheets may be included in the
document or linked externally.
<li><strong>User</strong>: The user may be able to specify style
information for a particular document. For example, the user may
specify a file that contains a style sheet or the user agent may
provide an interface that generates a user style sheet (or behaves as
if it did).
<li><strong>User agent</strong>: <a
href="conform.html#conformance">Conforming user agents</a> must apply
a <span class="index-def" title="default style sheet"><a
name="default-style-sheet"><dfn>default style sheet</dfn></a></span>
(or behave as if they did). A user agent's default style sheet should
present the
elements of the document language in ways that satisfy general
presentation expectations for the document language (e.g., for visual
browsers, the EM element in HTML is presented using an italic
font). See <a href="sample.html">A sample style sheet for HTML
</a> for a recommended default style sheet for HTML documents.
<p class="note">Note that the user may modify system settings (e.g.,
system colors) that affect the default style sheet. However, some user
agent implementations make it impossible to change the values in the
default style sheet.
</ul>
<P>Style sheets from these three origins will overlap in scope, and
they interact according to the cascade.
<P>The CSS <span class="index-def" title="cascade">cascade</span>
assigns a weight to each style rule. When several rules apply, the one
with the greatest weight takes precedence.
<P>By default, rules in author style sheets have more weight than
rules in user style sheets. Precedence is reversed, however, for
"!important" rules. All user and author rules have more weight
than rules in the UA's default style sheet.
<H3><a name="cascading-order">Cascading order</a></H3>
<P>To find the value for an element/property combination, user agents
must apply the following sorting order:</p>
<OL>
<LI>
Find all declarations that apply to the element and property in
question, for the target <a href="media.html">media type</a>.
Declarations apply if the associated selector <A
HREF="selector.html">matches</A> the element in question and the
target medium matches the media list on all @media rules
containing the declaration and on all links on the path through
which the style sheet was reached.
<LI>Sort according to importance (normal or important)
and origin (author, user, or user agent). In ascending order of
precedence:
<ol>
<li>user agent declarations
<
8000
div id="LC310" class="react-file-line html-div" data-testid="code-cell" data-line-number="310" style="position:relative"><li>user normal declarations
<li>author normal declarations
<li>author important declarations
<li>user important declarations
</ol>
<LI>
Sort rules with the same importance and origin by <a href="#specificity">specificity</a>
of selector: more specific
selectors will override more general ones. Pseudo-elements and
pseudo-classes are counted as normal elements and classes,
respectively.
<LI>Finally, sort by order specified: if two declarations have the
same weight, origin and specificity, the latter specified wins.
Declarations in imported style sheets are considered to be before any
declarations in the style sheet itself.
</OL>
<P>Apart from the "!important" setting on individual declarations,
this strategy gives author's style sheets higher weight than those of
the reader. User agents must give the user the ability to turn off the
influence of specific author style sheets, e.g., through a pull-down
menu. Conformance to UAAG 1.0 checkpoint 4.14 satisfies this condition [[UAAG10]].
<H3><a name="important-rules">!important rules</a></H3>
<P>CSS attempts to create a balance of power between author
and user style sheets. By default, rules in an author's style
sheet override those in a user's style sheet (see cascade
rule 3).
<P>However, for balance, an "!important" declaration (the delimiter token
"!" and keyword "important" follow the declaration) takes precedence over
a normal declaration. Both author and user style sheets may contain
"!important" declarations, and user "!important" rules override author
"!important" rules. This CSS feature improves accessibility
of documents by giving users with special requirements (large
fonts, color combinations, etc.) control over presentation.
<P>Declaring a <span class="index-inst" title="shorthand
property">shorthand property</span> (e.g., <span
class="propinst-background">'background'</span>) to be "!important" is
equivalent to declaring all of its sub-properties to be "!important".
<div class="example">
<P>The first rule in the user's style sheet in the following example
contains an "!important" declaration, which overrides the corresponding
declaration in the author's style sheet. The second declaration
will also win due to being marked "!important". However, the third
rule in the user's style sheet is not "!important" and will therefore
lose to the second rule in the author's style sheet (which happens to
set style on a shorthand property). Also, the third author rule will
lose to the second author rule since the second rule is
"!important". This shows that "!important" declarations have a
function also within author style sheets.
<PRE>
/* From the user's style sheet */
p { text-indent: 1em ! important }
p { font-style: italic ! important }
p { font-size: 18pt }
/* From the author's style sheet */
p { text-indent: 1.5em !important }
p { font: normal 12pt sans-serif !important }
p { font-size: 24pt }
</PRE>
</div>
<H3><a name="specificity">Calculating a selector's specificity</a></H3>
<P>A selector's specificity is calculated as follows:</p>
<ul>
<li>count 1 if the declaration is from is a 'style' attribute rather
than a rule with a
selector, 0 otherwise (= a) (In HTML, values of an element's "style"
attribute are style sheet rules. These rules have no selectors, so
a=1, b=0, c=0, and d=0.)
<li>count the number of ID attributes in the selector (= b)
<li>count the number of other attributes and pseudo-classes
in the selector (= c)
<li>count the number of element names and pseudo-elements in the selector (= d)
</ul>
<p>The specificity is based only on the form of the selector. In
particular, a selector of the form "[id=p33]" is counted as an
attribute selector (a=0, b=0, c=1, d=0), even if the id attribute is
defined as an "ID" in the source document's DTD.
<P>Concatenating the four numbers a-b-c-d (in a number system with a large
base) gives the specificity.
<div class="example"><P>
Some examples:
<PRE>
* {} /* a=0 b=0 c=0 d=0 -> specificity = 0,0,0,0 */
li {} /* a=0 b=0 c=0 d=1 -> specificity = 0,0,0,1 */
li:first-line {} /* a=0 b=0 c=0 d=2 -> specificity = 0,0,0,2 */
ul li {} /* a=0 b=0 c=0 d=2 -> specificity = 0,0,0,2 */
ul ol+li {} /* a=0 b=0 c=0 d=3 -> specificity = 0,0,0,3 */
h1 + *[rel=up]{} /* a=0 b=0 c=1 d=1 -> specificity = 0,0,1,1 */
ul ol li.red {} /* a=0 b=0 c=1 d=3 -> specificity = 0,0,1,3 */
li.red.level {} /* a=0 b=0 c=2 d=1 -> specificity = 0,0,2,1 */
#x34y {} /* a=0 b=1 c=0 d=0 -> specificity = 0,1,0,0 */
style="" /* a=1 b=0 c=0 d=0 -> specificity = 1,0,0,0 */
</PRE>
</div>
<div class="html-example">
<pre>
<HEAD>
<STYLE type="text/css">
#x97z { color: red }
</STYLE>
</HEAD>
<BODY>
<P ID=x97z style="color: green">
</BODY>
</pre>
<P>In the above example, the color of the P element would be
green. The declaration in the "style" attribute will override the one in
the STYLE element because of cascading rule 3, since it has a higher
specificity.
</div>
<H3><a name="preshint">Precedence of non-CSS presentational hints</a></H3>
<P>The UA may choose to honor presentational attributes in an HTML source
document. If so, these attributes are translated to the corresponding
CSS rules with specificity equal to 0, and are treated as if they were
inserted at the start of the author style sheet. They may therefore be
overridden by subsequent style sheet rules. In a transition phase,
this policy will make it easier for stylistic attributes to coexist
with style sheets.
<P>For HTML, any attribute that is not in the following list should be
considered presentational: abbr, accept-charset, accept, accesskey,
action, alt, archive, axis, charset, checked, cite, class, classid,
code, codebase, codetype, colspan, coords, data, datetime, declare,
defer, dir, disabled, enctype, for, headers, href, hreflang,
http-equiv, id, ismap, label, lang, language, longdesc, maxlength,
media, method, multiple, name, nohref, object, onblur, onchange,
onclick, ondblclick, onfocus, onkeydown, onkeypress, onkeyup, onload,
onload, onmousedown, onmousemove, onmouseout, onmouseover, onmouseup,
onreset, onselect, onsubmit, onunload, onunload, profile, prompt,
readonly, rel, rev, rowspan, scheme, scope, selected, shape, span,
src, standby, start, style, summary, title, type (except on LI, OL and
UL elements), usemap, value, valuetype, version.
<P>For other languages, all document language-based styling must be
translated to the corresponding CSS and either enter the cascade at
the user agent level or, as with HTML presentational hints, be treated
as author level rules with a specificity of zero placed at the start
of the author style sheet.
<div class="example">
<p>The following user style sheet would override the font weight of
'b' elements in all documents, and the color of 'font'
elements with color attributes in XML documents. It would not affect
the color of any 'font' elements with color attributes in HTML
documents:
<pre>
b { font-weight: normal; }
font[color] { color: orange; }
</pre>
<P>The following, however, would override the color of font elements in all documents:
<pre>
font[color] { color: orange ! important; }
</pre>
</div>
</BODY>
</html>
<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-declaration:"~/SGML/HTML4.decl"
sgml-default-doctype-name:"html"
sgml-minimize-attributes:t
sgml-nofill-elements:("pre" "style" "br")
sgml-live-element-indicator:t
End:
-->