CSS Cascading and Inheritance Level 7

Editor’s Draft,

More details about this document
This version:
https://drafts.csswg.org/css-cascade-7/
Previous Versions:
Issue Tracking:
CSSWG Issues Repository
Inline In Spec
Editors:
Elika J. Etemad / fantasai (Apple)
Miriam E. Suzanne (Invited Expert)
Tab Atkins Jr. (Google)
(Microsoft)
Suggest an Edit for this Spec:
GitHub Editor

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.

New in this level is § 2.1 Named Stylesheets: the `@sheet` block at-rule.

CSS is a language for describing the rendering of structured documents (such as HTML and XML) on screen, on paper, etc.

Status of this document

This is a public copy of the editors’ draft. It is provided for discussion only and may change at any moment. Its publication here does not imply endorsement of its contents by W3C. Don’t cite this document other than as work in progress.

Please send feedback by filing issues in GitHub (preferred), including the spec code “css-cascade” in the title, like this: “[css-cascade] …summary of comment…”. All issues and comments are archived. Alternately, feedback can be sent to the (archived) public mailing list www-style@w3.org.

This document is governed by the 03 November 2023 W3C Process Document.

1. Introduction and Missing Sections

This is a diff spec over CSS Cascading and Inheritance Level 6. It is currently an Exploratory Working Draft: if you are implementing anything, please use Level 6 as a reference. We will merge the Level 6 text into this draft once it reaches CR.

2. Stylesheet

A stylesheet is a collection of style rules.

These collections may exist as:

  1. An instance of file with the CSS Style Sheet Content-Type, embedded within a document.
  2. A collection of CSS rules within a document.
  3. CSSOM Stylesheet objects.
  4. Any of the above may be subdivided into a named stylesheet with the @sheet rule.

A sheet-name is a string identifying inner named stylesheets within a stylesheet.

Syntactically, a named stylesheet must include an explicit sheet-name, and is represented by the <sheet-name> in @sheet and @import rules, which is a single <ident> token:

<sheet-name> = <ident>

2.1. Named Stylesheets: the `@sheet` block at-rule

A named stylesheet may be declared by using an @sheet block at-rule, assigning its child style rules into that sheet.

This sheet-assignment syntax is:

@sheet <sheet-name> {
  <rule-list>
}

Such @sheet block rules have the same restrictions and processing as a conditional group rule [CSS-CONDITIONAL-3] with a false condition.

Note: This means that rules within an @sheet block are not applied until their named stylesheet is explicitly imported into another context.

<style>
@sheet framework {
  h1 { color: maroon; }
}
</style>
<h1>Sample text</h1>

In this example, the h1 tag does not have the maroon color applied, as the @sheet named "framework" was not explicitly imported into another context.

@sheet block at-rules may not be nested within any other CSS rules.

2.2. Importing Specific Named Stylesheets: the from Keyword

<url-string> = [ <url> | <string> ]
<sheet-name-list> = [ <string> ][ ,<string> ]*

@import [ <sheet-name-list> from ]?
        [ <url-string> ]        
        [ layer | layer(<layer-name>) ]?
        <import-conditions> ;

<import-conditions> = [ supports( [ <supports-condition> | <declaration> ] ) ]?
                     <media-query-list>?

where:

A file with the CSS Style Sheet Content-Type and a URL of "foo.css":
@sheet framework {
  h1 { color: maroon; }
}

A document with the following CSS and HTML:

<style>
@import framework from url(foo.css);
</style>
<h1>Sample text</h1>

In this example, the h1 tag has the maroon color applied.

The following conditional @import rule only loads the named stylesheet with a name of "foo" from "narrow.css" when the UA supports display: flex, and only applies the stylesheet on a handheld device with a maximum viewport width of 400px.
@import foo from url("narrow.css") supports(display: flex) handheld and (max-width: 400px);
The following layer imports the named stylesheets named "foo" and "bar" from "tabs.css" into the framework.component layer, and an un-named layer, respectively:
@import foo, bar from url("tabs.css") layer(framework.component);
@import foo, bar from url("override.css") layer;

If a <url-string> is provided, it must be interpreted as a <url> with the same value.

The following lines are equivalent in meaning and illustrate both @import syntaxes (one with url() and one with a bare string):
@import "mystyle.css";
@import url("mystyle.css");

3. Sheet APIs

3.1. The CSSSheetRule interface

The CSSSheetRule interface represents the @sheet block rule:

[Exposed=Window]
interface CSSSheetRule : CSSGroupingRule {
  readonly attribute CSSOMString name;
};

Its name attribute represents the <sheet-name> declared by the @sheet block at-rule.

3.2. The SheetNameList Interface

An object that implements the SheetNameList interface defines a list of stylesheet names.

[Exposed=Window]
interface SheetNameList {
  readonly attribute unsigned long length;
  getter CSSOMString? item(unsigned long index);
};

3.3. Extensions to the CSSImportRule interface

The CSSImportRule interface is extended as follows:

partial interface CSSImportRule {
  [SameObject] readonly attribute SheetNameList sheetNames;
  [SameObject] readonly attribute StyleSheetList namedStyleSheets;
};

Its sheetNames attribute represents a list of <sheet-name> definitions declared by the @sheet block at-rule in the order they are listed.

Its namedStyleSheets attribute represents the list of imported named stylesheets in the order they are imported.

4. Changes

This appendix is informative.

4.1. Additions Since Level 6

The following features have been added since Level 6:

4.2. Additions Since Level 5

The following features have been added since Level 5:

4.3. Additions Since Level 4

The following features have been added since Level 4:

4.4. Additions Since Level 3

The following features have been added since Level 3:

4.5. Additions Since Level 2

The following features have been added since Level 2:

Acknowledgments

David Baron, Tantek Çelik, Keith Grant, Giuseppe Gurgone, Theresa O’Connor, Florian Rivoal, Noam Rosenthal, Simon Sapin, Jen Simmons, Nicole Sullivan, Lea Verou, and Boris Zbarsky contributed to this specification.

5. Privacy Considerations

6. Security Considerations

Conformance

Document conventions

Conformance requirements are expressed with a combination of descriptive assertions and RFC 2119 terminology. The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in the normative parts of this document are to be interpreted as described in RFC 2119. However, for readability, these words do not appear in all uppercase letters in this specification.

All of the text of this specification is normative except sections explicitly marked as non-normative, examples, and notes. [RFC2119]

Examples in this specification are introduced with the words “for example” or are set apart from the normative text with class="example", like this:

This is an example of an informative example.

Informative notes begin with the word “Note” and are set apart from the normative text with class="note", like this:

Note, this is an informative note.

Advisements are normative sections styled to evoke special attention and are set apart from other normative text with <strong class="advisement">, like this: UAs MUST provide an accessible alternative.

Tests

Tests relating to the content of this specification may be documented in “Tests” blocks like this one. Any such block is non-normative.


Conformance classes

Conformance to this specification is defined for three conformance classes:

style sheet
A CSS style sheet.
renderer
A UA that interprets the semantics of a style sheet and renders documents that use them.
authoring tool
A UA that writes a style sheet.

A style sheet is conformant to this specification if all of its statements that use syntax defined in this module are valid according to the generic CSS grammar and the individual grammars of each feature defined in this module.

A renderer is conformant to this specification if, in addition to interpreting the style sheet as defined by the appropriate specifications, it supports all the features defined by this specification by parsing them correctly and rendering the document accordingly. However, the inability of a UA to correctly render a document due to limitations of the device does not make the UA non-conformant. (For example, a UA is not required to render color on a monochrome monitor.)

An authoring tool is conformant to this specification if it writes style sheets that are syntactically correct according to the generic CSS grammar and the individual grammars of each feature in this module, and meet all other conformance requirements of style sheets as described in this module.

Partial implementations

So that authors can exploit the forward-compatible parsing rules to assign fallback values, CSS renderers must treat as invalid (and ignore as appropriate) any at-rules, properties, property values, keywords, and other syntactic constructs for which they have no usable level of support. In particular, user agents must not selectively ignore unsupported component values and honor supported values in a single multi-value property declaration: if any value is considered invalid (as unsupported values must be), CSS requires that the entire declaration be ignored.

Implementations of Unstable and Proprietary Features

To avoid clashes with future stable CSS features, the CSSWG recommends following best practices for the implementation of unstable features and proprietary extensions to CSS.

Non-experimental implementations

Once a specification reaches the Candidate Recommendation stage, non-experimental implementations are possible, and implementors should release an unprefixed implementation of any CR-level feature they can demonstrate to be correctly implemented according to spec.

To establish and maintain the interoperability of CSS across implementations, the CSS Working Group requests that non-experimental CSS renderers submit an implementation report (and, if necessary, the testcases used for that implementation report) to the W3C before releasing an unprefixed implementation of any CSS features. Testcases submitted to W3C are subject to review and correction by the CSS Working Group.

Further information on submitting testcases and implementation reports can be found from on the CSS Working Group’s website at http://www.w3.org/Style/CSS/Test/. Questions should be directed to the public-css-testsuite@w3.org mailing list.

Index

Terms defined by this specification

Terms defined by reference

References

Normative References

[APPMANIFEST]
Marcos Caceres; et al. Web Application Manifest. URL: https://w3c.github.io/manifest/
[CSS-CASCADE-4]
Elika Etemad; Tab Atkins Jr.. CSS Cascading and Inheritance Level 4. URL: https://drafts.csswg.org/css-cascade-4/
[CSS-CASCADE-5]
Elika Etemad; Miriam Suzanne; Tab Atkins Jr.. CSS Cascading and Inheritance Level 5. URL: https://drafts.csswg.org/css-cascade-5/
[CSS-CASCADE-6]
Elika Etemad; Miriam Suzanne; Tab Atkins Jr.. CSS Cascading and Inheritance Level 6. URL: https://drafts.csswg.org/css-cascade-6/
[CSS-CONDITIONAL-3]
Chris Lilley; David Baron; Elika Etemad. CSS Conditional Rules Module Level 3. URL: https://drafts.csswg.org/css-conditional-3/
[CSS-CONDITIONAL-5]
Chris Lilley; et al. CSS Conditional Rules Module Level 5. URL: https://drafts.csswg.org/css-conditional-5/
[CSS-SYNTAX-3]
Tab Atkins Jr.; Simon Sapin. CSS Syntax Module Level 3. URL: https://drafts.csswg.org/css-syntax/
[CSS-VALUES-3]
Tab Atkins Jr.; Elika Etemad. CSS Values and Units Module Level 3. URL: https://drafts.csswg.org/css-values-3/
[CSS-VALUES-4]
Tab Atkins Jr.; Elika Etemad. CSS Values and Units Module Level 4. URL: https://drafts.csswg.org/css-values-4/
[CSSOM-1]
Daniel Glazman; Emilio Cobos Álvarez. CSS Object Model (CSSOM). URL: https://drafts.csswg.org/cssom/
[FETCH]
Anne van Kesteren. Fetch Standard. Living Standard. URL: https://fetch.spec.whatwg.org/
[MEDIAQUERIES-4]
Florian Rivoal; Tab Atkins Jr.. Media Queries Level 4. URL: https://drafts.csswg.org/mediaqueries-4/
[RFC2119]
S. Bradner. Key words for use in RFCs to Indicate Requirement Levels. March 1997. Best Current Practice. URL: https://datatracker.ietf.org/doc/html/rfc2119
[WEBIDL]
Edgar Chen; Timothy Gu. Web IDL Standard. Living Standard. URL: https://webidl.spec.whatwg.org/

Informative References

[CSS-DISPLAY-4]
Elika Etemad; Tab Atkins Jr.. CSS Display Module Level 4. URL: https://drafts.csswg.org/css-display/
[DOM]
Anne van Kesteren. DOM Standard. Living Standard. URL: https://dom.spec.whatwg.org/

IDL Index

[Exposed=Window]
interface CSSSheetRule : CSSGroupingRule {
  readonly attribute CSSOMString name;
};

[Exposed=Window]
interface SheetNameList {
  readonly attribute unsigned long length;
  getter CSSOMString? item(unsigned long index);
};

partial interface CSSImportRule {
  [SameObject] readonly attribute SheetNameList sheetNames;
  [SameObject] readonly attribute StyleSheetList namedStyleSheets;
};

Issues Index

This is a diff spec over CSS Cascading and Inheritance Level 6. It is currently an Exploratory Working Draft: if you are implementing anything, please use Level 6 as a reference. We will merge the Level 6 text into this draft once it reaches CR.
MDN

all

In all current engines.

Firefox27+Safari9.1+Chrome37+
Opera?Edge79+
Edge (Legacy)?IENone
Firefox for Android?iOS Safari?Chrome for Android?Android WebView?Samsung Internet?Opera Mobile?
MDN

inherit

In all current engines.

Firefox1+Safari1+Chrome1+
Opera4+Edge79+
Edge (Legacy)12+IE8+
Firefox for Android?iOS Safari?Chrome for Android?Android WebView?Samsung Internet?Opera Mobile?
MDN

initial

In all current engines.

Firefox19+Safari1.2+Chrome1+
Opera?Edge79+
Edge (Legacy)13+IENone
Firefox for Android?iOS Safari?Chrome for Android?Android WebView?Samsung Internet?Opera Mobile?
MDN

revert

In all current engines.

Firefox67+Safari9.1+Chrome84+
Opera?Edge84+
Edge (Legacy)?IENone
Firefox for Android?iOS Safari?Chrome for Android?Android WebView?Samsung Internet?Opera Mobile?
MDN

unset

In all current engines.

Firefox27+Safari9.1+Chrome41+
Opera?Edge79+
Edge (Legacy)13+IENone
Firefox for Android?iOS Safari?Chrome for Android?Android WebView?Samsung Internet?Opera Mobile?