-
Notifications
You must be signed in to change notification settings - Fork 790
Expand file tree
/
Copy pathOverview.src.html
More file actions
924 lines (766 loc) · 34.3 KB
/
Overview.src.html
File metadata and controls
924 lines (766 loc) · 34.3 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
10000
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
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
<h1>CSS Cascading and Inheritance Level 3</h1>
<pre class='metadata'>
Shortname: css-cascade
Level: 3
Status: ED
ED: http://dev.w3.org/csswg/css-cascade/
TR: http://www.w3.org/TR/css3-cascade/
Editor: Håkon Wium Lie, Opera Software, howcome@opera.com
Editor: fantasai, Mozilla, http://fantasai.inkedblade.net/contact
Editor: Tab Atkins Jr., Google, http://xanthir.com/contact/
Previous Version: http://www.w3.org/TR/2013/WD-css-cascade-3-20130730/
Previous Version: http://www.w3.org/TR/2013/WD-css3-cascade-20130103/
Previous Version: http://www.w3.org/TR/2005/WD-css3-cascade-20051215/
Abstract: This CSS module describes how to collate style rules and assign values to all properties on all elements. By way of cascading and inheritance, values are propagated for all properties on all elements.
Ignored Terms: auto, flex items
Link Defaults: css21 (property) display
</pre>
<h2 id="intro">
Introduction</h2>
<p>
One of the fundamental design principles of CSS is <i title="cascade">cascading</i>,
which allows several style sheets to influence the presentation of a document.
When different declarations try to set a value for the same element/property combination,
the conflicts must somehow be resolved.
<p>
The opposite problem arises when no declarations try to set a the value for an element/property combination.
In this case, a value is be found by way of <i>inheritance</i>
or by looking at the property's <i>initial value</i>.
<p>
The <a href="#cascade">cascading</a> and <a href="#defaulting">defaulting</a> process takes a set of declarations as input,
and outputs a <i>specified value</i> for each property on each element.
<p>
The rules for finding the specified value for all properties on all elements in the document are described in this specification.
The rules for finding the specified values in the page context and its margin boxes are described in [[CSS3PAGE]].
<h2 id="at-import">
Importing Style Sheets: the ''@import'' rule</h2>
<p>
The <dfn>''@import''</dfn> rule allows users to import style rules from other style sheets.
Any ''@import'' rules must precede all other at-rules and style rules in a style sheet
(besides ''@charset'', which must be the first thing in the style sheet if it exists),
or else the ''@import'' rule is invalid.
The syntax of ''@import'' is:
<pre class='prod'><dfn><import-rule></dfn> = @import [ <url> | <string> ] <media-query-list>? ;</pre>
<p>
If a <var><string></var> is provided,
it must be interpreted as a url with the same value.
<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):
<pre><!--
-->@import "mystyle.css";
<!--
-->@import url("mystyle.css");</pre>
</div>
If an ''@import'' rule refers to a valid stylesheet,
user agents must treat the contents of the stylesheet as if they were written in place of the ''@import'' rule.
<p class='example'>
For example, declarations in style rules from imported stylesheets interact with the cascade
as if they were written literally into the stylesheet at the point of the ''@import''.
Similarly, style rules in a stylesheet imported into a scoped stylesheet
are scoped in the same way.
<p>
An ''@import'' rule can be media-dependent:
such media-dependent imports include a comma-separated list of “media queries” after the URI,
which specify to which media the imported style sheet applies.
In the absence of any media query, the import is unconditional.
(Specifying ''all'' for the medium has the same effect.)
<p>
The evaluation and full syntax of the expressions after the URL
is defined by the <a href="http://www.w3.org/TR/css3-mediaqueries/">Media Queries</a> specification [[!MEDIAQ]].
If the media query does not match,
the rules in the imported stylesheet do not apply,
exactly as if the imported stylesheet were wrapped in an ''@media'' block with the given media query.
User agents may therefore avoid fetching a media-dependent import
as long as the media query does not match.
<div class=example>
<p>
The following rules illustrate how ''@import'' rules can be made media-dependent:
<pre><!--
-->@import url("fineprint.css") print;
<!--
-->@import url("bluish.css") projection, tv;
<!--
-->@import url("narrow.css") handheld and (max-width: 400px);</pre>
</div>
<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.
<p class='note'>
Note: This does not place any requirements on resource fetching,
only how the style sheet is reflected in the CSSOM and used in specs such as this one.
Assuming appropriate caching,
it is perfectly appropriate for a UA to fetch a style sheet only once,
even though it's linked or imported multiple times.
<p>
The <i>origin</i> of an imported style sheet is the same as the <i>origin</i> of the style sheet that imported it.
<h3 id='content-type'>
Content-Type of CSS Style Sheets</h3>
<p>
The processing of imported style sheets depends on the actual type of the linked resource.
If the resource does not have <a href="http://www.whatwg.org/specs/web-apps/current-work/multipage/fetching-resources.html#content-type">Content-Type metadata</a>,
or the host document is in <a href="http://www.whatwg.org/specs/web-apps/current-work/multipage/infrastructure.html#quirks-mode">quirks mode</a>
and has the <a href="http://www.whatwg.org/specs/web-apps/current-work/multipage/origin-0.html#same-origin">same origin</a> as the imported style sheet,
the type of the linked resource is <code>text/css</code>.
Otherwise, the type is determined from its <a href="http://www.whatwg.org/specs/web-apps/current-work/multipage/fetching-resources.html#content-type">Content-Type metadata</a>.
<p>
If the linked resource's type is <code>text/css</code>,
it must be interpreted as a CSS style sheet.
Otherwise, it must be interpreted as a network error.
<h2 id='shorthand'>
Shorthand Properties</h2>
<p>
Some properties are <dfn export title="shorthand property | shorthand">shorthand properties</dfn>,
meaning that they allow authors to specify the values of several properties with a single property.
A <i>shorthand property</i> sets all of its <dfn export title="longhand | longhand property | sub-property">longhand sub-properties</dfn>,
exactly as if expanded in place.
<div class='example'>
<p>
For example, the 'font' property
is a <i>shorthand</i> property for setting <a property>font-style</a>, <a property>font-variant</a>, <a property>font-weight</a>, 'font-size', 'line-height', and <a property>font-family</a> all at once.
The multiple declarations of this example:
<pre>
h1 {
font-weight: bold;
font-size: 12pt;
line-height: 14pt;
font-family: Helvetica;
font-variant: normal;
font-style: normal;
}</pre>
<p>can therefore be rewritten as
<pre>h1 { font: bold 12pt/14pt Helvetica }</pre>
</div>
<p>
When values are omitted from a <i>shorthand</i> form,
unless otherwise defined,
each “missing” <i>sub-property</i> is assigned its <i>initial value</i>.
<div class='note'>
<p>
This means that a <i>shorthand</i> property declaration always sets <em title=''>all</em> of its <i>sub-properties</i>,
even those that are not explicitly set.
Carelessly used, this might result in inadvertently resetting some <i>sub-properties</i>.
Carefully used, a <i>shorthand</i> can guarantee a “blank slate”
by resetting <i>sub-properties</i> inadvertently cascaded from other sources.
<p>
For example, writing ''background: green'' rather than ''background-color: green''
ensures that the background color overrides any earlier declarations
that might have set the background to an image.
</div>
<p>
In some cases, a <i>shorthand</i> might have different syntax
or special keywords
that don't directly correspond to values of its <i>sub-properties</i>.
(In such cases, the <i>shorthand</i> will explicitly define the expansion of its values.)
<p>
If a <i>shorthand</i> is specified as one of the <a href="http://www.w3.org/TR/css3-values/#common-keywords">CSS-wide keywords</a> [[!CSS3VAL]],
it sets all of its <i>sub-properties</i> to that keyword.
(Note that these keywords cannot be combined with other values in a single declaration, not even in a shorthand.)
<p>
Declaring a <i>shorthand</i> property to be ''!important''
is equivalent to declaring all of its <i>sub-properties</i> to be ''!important''.
<h3 id="all-shorthand">
Resetting All Properties: the ''all'' property</h3>
<table class="propdef">
<tr>
<th>Name:
<td><dfn>all</dfn>
<tr>
<th>Value:
<td>initial | inherit | unset
<tr>
<th>Initial:
<td>See individual properties
<tr>
<th>Applies to:
<td>See individual properties
<tr>
<th>Inherited:
<td>See individual properties
<tr>
<th>Percentages:
<td>See individual properties
<tr>
<th>Media:
<td>See individual properties
<tr>
<th>Computed value:
<td>See individual properties
<tr>
<th>Animatable:
<td>See individual properties
</table>
<p>
The ''all'' property is a <i>shorthand</i> that resets <em title=''>all</em> CSS properties
except 'direction' and 'unicode-bidi'.
It only accepts the <a href="http://www.w3.org/TR/css3-values/#common-keywords">CSS-wide keywords</a>.
<p class='note'>
The excepted properties are actually markup-level features,
and <a href="http://www.w3.org/TR/css3-writing-modes/#text-direction">should not be set in the author's style sheet</a>.
(They exist as CSS properties only to style document languages not supported by the UA.)
Authors should use the appropriate markup, such as HTML's <code>dir</code> attribute, instead.
[[!CSS3-WRITING-MODES]]
<div class='example'>
<p>
For example, if an author specifies ''all: initial'' on an element
it will block all inheritance and reset all properties,
as if no rules appeared in the author, user, or user-agent levels of the cascade.
<p>
This can be useful for the root element of a "widget" included in a page,
which does not wish to inherit the styles of the outer page.
Note, however, that any "default" style applied to that element
(such as, e.g. ''display: block'' from the UA style sheet on block elements such as <code><div></code>)
will also be blown away.
</div>
<h2 id="value-stages">
Value Processing</h2>
<p>
Once a user agent has parsed a document and constructed a document tree,
it must assign,
to every element in the tree,
and correspondingly to every box in the formatting structure,
a value to every property that applies to the target media type.
<p>
The final value of a CSS property for a given element or box
is the result of a multi-step calculation:
<ul>
<li>
First, all the <i>declared values</i> applied to an element are collected,
for each property on each element.
There may be zero or many <i>declared values</i> applied to the element.
<li>
Cascading yields the <i>cascaded value</i>.
There is at most one <i>cascaded value</i> per property per element.
<li>
Defaulting yields the <i>specified value</i>.
Every element has exactly one <i>specified value</i> per property.
<li>
Resolving value dependencies yields the <i>computed value</i>.
Every element has exactly one <i>computed value</i> per property.
<li>
Formatting the document yields the <i>used value</i>.
An element only has a <i>used value</i> for a given property
if that property applies to the element.
<li>
Finally, the used value is transformed to the <i>actual value</i>
based on constraints of the display environment.
As with the <i>used value</i>, there may or may not be an <i>actual value</i>
for a given property on an element.
</ul>
<h3 id="declared">
Declared Values</h3>
<p>
Each property declaration <a href="#filtering">applied to an element</a>
contributes a <dfn export>declared value</dfn> for that property
associated with the element.
See <a href="#filtering">Filtering Declarations</a> for details.
<p>
These values are then processed by the <i>cascade</i>
to choose a single “winning value”.
<h3 id="cascaded">
Cascaded Values</h3>
<p>
The <dfn export>cascaded value</dfn> represents the result of <a href="#cascade">the cascade</a>:
it is the <i>declared value</i> that wins the cascade
(is sorted first in the <i>output of the cascade</i>).
If the <i>output of the cascade</i> is an empty list,
there is no <i>cascaded value</i>.
<h3 id="specified">
Specified Values</h3>
<p>
The <dfn export>specified value</dfn> the value of a given property that the style sheet authors intended for that element.
It is the result of putting the <i>cascaded value</i> through the <a href="#defaulting">defaulting</a> processes,
guaranteeing that a <i>specified value</i> exists for every property on every element.
<p>
In many cases, the <i>specified value</i> is the <i>cascaded value</i>.
However, if there is no <i>cascaded value</i> at all,
the <i>specified value</i> is <a href="#defaulting">defaulted</a>.
The ''initial'' and ''inherit'' keywords
are handled specially when they are the <i>cascaded value</i> of a property,
<h3 id="computed">
Computed Values</h3>
<p>
The <dfn export>computed value</dfn> is the result of resolving the <i>specified value</i>
as defined in the “Computed Value” line of the property definition table,
generally absolutizing it in preparation for <i>inheritance</i>.
<p class="note">
The <i>computed value</i> is the value that is transferred from parent to child during <i>inheritance</i>.
For historical reasons,
it is not necessarily the value returned by the <code>getComputedStyle()</code> function.
<div class="example">
A <i>specified value</i> can be either absolute (i.e., not relative to another value, as in '
7299
9;red'' or ''2mm'')
or relative (i.e., relative to another value, as in ''auto'', ''2em'').
Computing a relative value generally absolutizes it:
<ul>
<li>
values with relative units
(''em'', ''ex'', ''vh'', ''vw'')
must be made absolute by multiplying with the appropriate reference size
<li>
certain keywords
(e.g., ''smaller'', ''bolder'')
must be replaced according to their definitions
<li>
percentages on some properties must be multiplied by a reference value
(defined by the property)
<li>
valid relative URLs must be resolved to become absolute.
</ul>
<p>
See examples (f), (g) and (h) in the <a href="#stages-examples">table below</a>.
</div>
<p class="note">
In general, the <i>computed value</i> resolves the <i>specified value</i>
as far as possible without laying out the document
or performing other expensive or hard-to-parallelize operations,
such as resolving network requests
or retrieving values other than from the element and its parent.
<p>
The <i>computed value</i> exists even when the property does not apply
(as defined by the “Applies To” line).
However, some properties may change how they determine the <i>computed value</i>
based on whether the property applies to the element.
<h3 id='used'>
Used Values</h3>
<p>
The <dfn export>used value</dfn> is the result of taking the <i>computed value</i>
and completing any remaining calculations to make it the absolute theoretical value
used in the layout of the document.
If the property does not apply to this element,
then the element has no <i>used value</i> for that property.
<p class='example'>
For example, a declaration of ''width: auto'' can't be resolved into a length without knowing the layout of the element's ancestors,
so the <i>computed value</i> is ''auto'',
while the <i>used value</i> is an absolute length, such as ''100px''. [[CSS21]]
<p class='example'>
As another example, a <code><div></code> might have a computed 'break-before' value of ''auto'',
but acquire a used 'break-before' value of ''page'' by propagation from its first child. [[CSS3-BREAK]]
<p class='example'>
Lastly, if a property does not apply to an element,
it has no <i>used value</i>;
so, for example, the 'flex' property has no <i>used value</i>
on elements that aren't <i>flex items</i>.
<h3 id="actual">
Actual Values</h3>
<p>
A <i>used value</i> is in principle ready to be used,
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 <i title="used value">used</i> width.
Also, the font size of an element may need adjustment based on the availability of fonts
or the value of the 'font-size-adjust' property.
The <dfn export>actual value</dfn> is the used value after any such adjustments have been made.
<p class="note">
By probing the actual values of elements,
much can be learned about how the document is laid out.
However, not all information is recorded in the actual values.
For example, the actual value of the 'page-break-after' property
does not reflect whether there is a page break or not after the element.
Similarly, the actual value of 'orphans'
does not reflect how many orphan lines there is in a certain element.
See examples (j) and (k) in the <a href="#stages-examples">table below</a>.
<h3 id="stages-examples">
Examples</h3>
<table class="data">
<thead>
<tr>
<th>
<th>Property
<th>Winning declaration
<th>Cascaded value
<th>Specified value
<th>Computed value
<th>Used value
<th>Actual value
<tbody>
<tr>
<td>(a)
<th>'text-align'
<td><code class="declaration">text-align: left</code>
<td>''left''
<td>''left''
<td>''left''
<td>''left''
<td>''left''
<tr>
<td>(b)
<th>'border-top-width', 'border-right-width', 'border-bottom-width', 'border-left-width'
<td><code class="declaration">border-width: inherit</code>
<td>''inherit''
<td class="say">''4.2px''
<td>''4.2px''
<td>''4.2px''
<td>''4px''
<tr>
<td>(c)
<th>'width'
<td><small>(none)</small>
<td><small>(none)</small>
<td>''auto'' <small>(initial value)</small>
<td>''auto''
<td>''120px''
<td>''120px''
<tr>
<td>(d)
<th>'list-style-position'
<td><code class="declaration">list-style-position: inherit</code>
<td>''inherit''
<td class="say">''inside''
<td>''inside''
<td>''inside''
<td>''inside''
<tr>
<td>(e)
<th>'list-style-position'
<td><code class="declaration">list-style-position: initial</code>
<td>''initial''
<td>''outside'' <small>(initial value)</small>
<td>''outside''
<td>''outside''
<td>''outside''
<tr>
<td>(f)
<th>'font-size'
<td><code class="declaration">font-size: 1.2em</code>
<td>''1.2em''
<td>''1.2em''
<td class="say">''14.1px''
<td>''14.1px''
<td>''14px''
<tr>
<td>(g)
<th>'width'
<td><code class="declaration">width: 80%</code>
<td>''80%''
<td>''80%''
<td>''80%''
<td class="say">''354.2px''
<td>''354px''
<tr>
<td>(h)
<th>'width'
<td><code class="declaration">width: auto</code>
<td>''auto''
<td>''auto''
<td>''auto''
<td class="say">''134px''
<td>''134px''
<tr>
<td>(i)
<th>'height'
<td><code class="declaration">height: auto</code>
<td>''auto''
<td>''auto''
<td>''auto''
<td class="say">''176px''
<td>''176px''
<tr>
<td>(j)
<th>'page-break-after'
<td><small>(none)</small>
<td><small>(none)</small>
<td>''auto'' <small>(initial value)</small>
<td>''auto''
<td>''auto''
<td>''auto''
<tr>
<td>(k)
<th>'orphans'
<td><code class="declaration">orphans: 3</code>
<td>''3''
<td>''3''
<td>''3''
<td>''3''
<td>''3''
</table>
<h2 id='filtering'>
Filtering</h2>
<p>
In order to find the <i>declared values</i>,
implementations must first identify all declarations that apply to each element.
A declaration applies to an element if:
<ul>
<li>
It belongs to a style sheet that currently applies to this document.
<li>
It is not qualified by a conditional rule [[!CSS3-CONDITIONAL]] with a false condition.
<li>
It belongs to a style rule whose selector matches the element. [[!SELECT]]
(Taking <a href="http://www.w3.org/TR/selectors4/#scoping">scoping</a> into account, if necessary.)
<li>
It is syntactically valid:
the declaration's property is a known property name,
and the declaration's value matches the syntax for that property.
</ul>
<p>
The values of the declarations that apply form,
for each property on each element,
a list of <i>declared values</i>.
The next section,
the <i>cascade</i>,
prioritizes these lists.
<h2 id='cascading'>
Cascading</h2>
<p>
The <dfn export>cascade</dfn>
takes a unordered list of <i>declared values</i>
for a given property on a given element,
sorts them by their declaration’s precedence as determined below,
and outputs a single <i>cascaded value</i>.
<p>
The cascade sorts declarations according to the following criteria,
in descending order of priority:
<dl>
<dt id='cascade-origin'>Origin and Importance
<dd>
The <i>origin</i> of a declaration is based on where it comes from
and its <i title="important">importance</i> is whether or not it is declared ''!important'' (see below).
The precedence of the various <i>origins</i> is, in descending order:
<ol>
<li>Transition declarations [[!CSS3-TRANSITIONS]]
<li>Important user agent declarations
<li>Important user declarations
<li>Important override declarations [[!DOM-LEVEL-2-STYLE]]
<li>Important author declarations
<li>Animation declarations [[!CSS3-ANIMATIONS]]
<li>Normal override declarations [[!DOM-LEVEL-2-STYLE]]
<li>Normal author declarations
<li>Normal user declarations
<li>Normal user agent declarations
</ol>
<p>
Declarations from <i>origins</i> earlier in this list win over declarations from later <i>origins</i>.
<dt id='cascade-scope'>Scope
<dd>
A declaration can be <dfn export>scoped</dfn> to a subtree of the document
so that it only affects its <dfn export>scoping element</dfn> and that element's descendants.
For example, [[HTML5]] defines scoped <code><style></code> elements,
whose style sheets are scoped to the element's parent.
<p>
If the <i>scoping elements</i> of two declarations
have an ancestor/descendant relationship,
then for normal rules the declaration whose <i>scoping element</i> is the descendant wins,
and for important rules the declaration whose <i>scoping element</i> is the ancestor wins.
<p class="note">
In other words, for normal declarations the inner scope's declarations override,
but for <code>!important</code> rules <em>outer</em> scope's override.
<p>
For the purpose of this step,
all unscoped declarations are considered to be <i>scoped</i> to the root element.
Normal declarations from style attributes
are considered to be <i>scoped</i> to the element with the attribute,
whereas important declarations from style attributes
are considered to be <i>scoped</i> to the root element.
[[!CSSSTYLEATTR]]
<p class="note">
This odd handling of <code>!important</code> style attribute declarations
is to match the behavior defined in CSS Levels 1 and 2,
where style attributes simply have higher specificity than any other author rules. [[CSS21]]
<dt id='cascade-specificity'>Specificity
<dd>
The <a href="http://www.w3.org/TR/selectors/#specificity">Selectors module</a> [[!SELECT]] describes how to compute the specificity of a selector.
Each declaration has the same specificity as the style rule it appears in.
For the purpose of this step,
declarations that do not belong to a style rule
(such as the <a href="http://www.w3.org/TR/css-style-attr/#interpret">contents of a style attribute</a>)
are considered to have a specificity higher than any selector.
The declaration with the highest specificity wins.
<dt id='cascade-order'>Order of Appearance
<dd>
The last declaration in document order wins.
For this purpose:
<ul>
<li>Declarations from <a at-rule title="@import">imported style sheets</a>
are ordered as if their style sheets were substituted in place of the ''@import'' rule.
<li>Declarations from style sheets independently linked by the originating document
are treated as if they were concatenated in linking order,
as determined by the host document language.
<li>Declarations from style attributes
are ordered according to the document order of the element the style attribute appears on,
and are all placed after any style sheets.
</ul>
</dl>
<p>
The <dfn>output of the cascade</dfn>
is a (potentially empty) sorted list of <i>declared values</i> for each property on each element.
<h3 id='cascading-origins'>
Cascading Origins</h3>
<p>
Each style rule has an <dfn export>origin</dfn>,
which determines where it enters the cascade.
CSS defines three core <i>origins</i>:
<dl>
<dt id='cascade-origin-author'>Author
<dd>
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.
<dt id='cascade-origin-user'>User
<dd>
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).
<dt id='cascade-origin-ua'>User agent
<dd>
Conforming user agents must apply a default style sheet
(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 e.g. the <a href="http://www.whatwg.org/specs/web-apps/current-work/multipage/rendering.html#the-css-user-agent-style-sheet-and-presentational-hints">HTML user agent style sheet</a>. [[HTML5]]
</dl>
<p>
Extensions to CSS define the following additional <i>origins</i>:
<dl>
<dt id='cascade-origin-override'>Override
<dd>
DOM Level 2 Style [[!DOM-LEVEL-2-STYLE]] defines an interface for “override” styles,
which enter the cascade at a higher level than other author rules.
<dt id='cascade-origin-animation'>Animation
<dd>
CSS Animations [[CSS3-ANIMATIONS]] generate “virtual” rules representing their effects when running.
<dt id='cascade-origin-transition'>Transition
<dd>
Like CSS Animations, CSS Transitions [[CSS3-TRANSITIONS]] generate “virtual” rules representing their effects when running.
</dl>
<h3 id='importance'>
Important Declarations: the ''!important'' annotation</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,
which override those in the user-agent's default style sheet.
To balance this, a declaration can be made <dfn export>important</dfn>,
which increases its weight in the cascade and inverts the order of precedence.
<p>
A declaration is <i>important</i> if it has a <dfn export>!important</dfn> annotation,
i.e. if the last two (non-whitespace, non-comment) tokens
in its value are the delimiter token ''!'' followed by the identifier token ''important''.
<div class='example'>
<pre>[hidden] { display: none !important; }</pre>
</div>
<p>
An <i>important</i> declaration takes precedence over a normal declaration.
Author and user style sheets may contain ''!important'' declarations,
with user ''!important'' declarations overriding author ''!important'' declarations.
This CSS feature improves accessibility of documents by giving users with special requirements
(large fonts, color combinations, etc.)
control over presentation.
<p>
Important declarations from all origins take precedence over animations.
This allows authors to override animated values in important cases.
(Animated values normally override all other rules.)
[[CSS3-ANIMATIONS]]
<p>
User agent style sheets may also contain ''!important'' declarations.
These override all author and user declarations.
<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 declaration in the second rule will also win due to being marked ''!important''.
However, the third declaration 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 <i>shorthand</i> property).
Also, the third author rule will lose to the second author rule since the second declaration 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 id="preshint">
Precedence of Non-CSS Presentational Hints</h3>
<p>
The UA may choose to honor presentational hints in a source document's markup,
for example the <code>bgcolor</code> attribute or <code><s></code> element in [[HTML5]].
All document language-based styling must be translated to corresponding CSS rules
and either enter the cascade at the user agent level or
be treated as author level rules with a specificity of zero placed at the start of the author style sheet.
A document language may define whether a presentational hint enters at the UA or author level of the cascade;
if so, the UA must behave accordingly.
For example, [[SVG11]] maps its presentation attributes into the author level.
<p class="note">
Presentational hints entering the cascade at the UA level can be overridden by author or user styles.
Presentational hints entering the cascade at the author level can be overridden by author styles,
but not by non-<code>!important</code> user styles.
Host languages should choose the appropriate level for presentational hints with these considerations in mind.
<h2 id="defaulting">
Defaulting</h2>
<p>
When the <i>cascade</i> does not result in a value,
the <i>specified value</i> must be found some other way.
<i>Inherited properties</i> draw their defaults from their parent element through <i>inheritance</i>;
all other properties take their <i>initial value</i>.
Authors can explicitly request inheritance or initialization
via the ''inherit'' and ''initial'' keywords.
<h3 id="initial-values">
Initial Values</h3>
<p>
Each property has an <dfn export>initial value</dfn>,
defined in the property's definition table.
If the property is not an <i>inherited property</i>,
and the <i>cascade</i> does not result in a value,
then the <i>specified value</i> of the property is its <i>initial value</i>.
<h3 id="inheriting">
Inheritance</h3>
<p>
<dfn export>Inheritance</dfn> propagates property values from parent elements to their children.
The <dfn export>inherited value</dfn> of a property on an element
is the <i>computed value</i> of the property on the element's parent element.
For the root element,
which has no parent element,
the <i>inherited value</i> is the <i>initial value</i> of the property.
<p>
(Pseudo-elements inherit according to a fictional tag sequence described for each pseudo-element [[!SELECT]].)
<p>
Some properties are <dfn export title="inherited property">inherited properties</dfn>,
as defined in their property definition table.
This means that,
unless the cascade results in a value,
the value will be determined by inheritance.
<p>
A property can also be explicitly inherited. See the ''inherit'' keyword.
<p class='note'>
Note that inheritance follows the document tree and is not intercepted by <a href="http://www.w3.org/TR/CSS21/visuren.html#box-gen">anonymous boxes</a>,
or otherwise affected by manipulations of the box tree.
<h3 id="defaulting-keywords">
Explicit Defaulting</h3>
<p>
Several CSS-wide property values are defined below;
declaring a property to have these values explicitly specifies a particular defaulting behavior.
As specified in <a href="http://www.w3.org/TR/css3-values/#common-keywords">CSS Values and Units Level 3</a> [[!CSS3VAL]],
all CSS properties can accept these values.
<h4 id="initial">
Resetting a Property: the ''initial'' keyword</h4>
<p>
If the <i>cascaded value</i> is the <dfn for=all>''initial''</dfn> keyword,
the property's <i>initial value</i> becomes its <i>specified value</i>.
<h4 id="inherit">
Explicit Inheritance: the ''inherit'' keyword</h4>
<p>
If the <i>cascaded value</i> of a property is the <dfn for=all>''inherit''</dfn> keyword,
the <i>inherited value</i> becomes the property's <i title="specified value">specified</i> and <i>computed values</i>.
<h4 id="inherit-initial">
Erasing All Declarations: the ''unset'' keyword</h4>
<p>
If the <i>cascaded value</i> of a property is the <dfn for=all>''unset''</dfn> keyword,
then if it is an inherited property, this is treated as ''inherit'',
and if it is not, this is treated as ''initial''.
This keyword effectively erases all <i>declared values</i> occurring earlier in the <i>cascade</i>,
correctly inheriting or not as appropriate for the property
(or all longhands of a <i>shorthand</i>).
<h2 id="changes">
Changes</h2>
<h3 id="changes-2013">
Changes Since the 30 July 2013 Last Call Working Draft</h3>
<p>The following changes were made to this specification since the
<a href="http://www.w3.org/TR/2013/WD-css-cascade-3-20130730/">30 July 2013 Last Call Working Draft</a>:
<ul>
<li>Clarified interaction of media-dependent ''@import'' statements and style sheet loading requirements.
</ul>
<p>A <a href="http://dev.w3.org/csswg/css-cascade/issues-lc-2013">Disposition of Comments</a> is available.
<h2 class="no-num" id="acknowledgments">Acknowledgments</h2>
<p>David Baron, Simon Sapin, and Boris Zbarsky contributed to this specification.