Skip to content

[css-syntax-3] Editorial: Linked to CSSOM #5765

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Dec 22, 2020
Merged

[css-syntax-3] Editorial: Linked to CSSOM #5765

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions css-syntax-3/Overview.bs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -255,7 +255,7 @@ Error Handling</h3>
Tokenizing and Parsing CSS</h2>

User agents must use the parsing rules described in this specification
to generate the CSSOM trees from text/css resources.
to generate the [[CSSOM]] trees from text/css resources.
Together, these rules define what is referred to as the CSS parser.

This specification defines the parsing rules for CSS documents,
Expand Down Expand Up @@ -2021,7 +2021,7 @@ Parse something according to a CSS grammar</h4>
Note: This algorithm,
and [=parse a comma-separated list according to a CSS grammar=],
are <em>usually</em> the only parsing algorithms other specs will want to call.
The remaining parsing algorithms are meant mostly for CSSOM
The remaining parsing algorithms are meant mostly for [[CSSOM]]
and related "explicitly constructing CSS structures" cases.
Consult the CSSWG for guidance first
if you think you need to use one of the other algorithms.
Expand Down Expand Up @@ -3391,7 +3391,7 @@ Serialization</h2>
If they do, this preserved information must have no effect on the parsing step.

This specification does not define how to serialize CSS in general,
leaving that task to the CSSOM and individual feature specifications.
leaving that task to the [[CSSOM]] and individual feature specifications.
In particular, the serialization of comments and whitespace is not defined.

The only requirement for serialization is that it must "round-trip" with parsing,
Expand Down