Skip to content
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

Jump to bottom

[css-cascade] 'output of the cascade' typo in all levels of Cascading & Inheritance spec? #9998

Open
mirisuzanne opened this issue Feb 26, 2024 · 1 comment
Open

[css-cascade] 'output of the cascade' typo in all levels of Cascading & Inheritance spec? #9998

mirisuzanne opened this issue Feb 26, 2024 · 1 comment
Labels
css-cascade-3 css-cascade-4 Current Work css-cascade-5 css-cascade-6 editorial

Comments

@mirisuzanne
Copy link
Contributor

At the end of the Cascade Sorting Order section, from cascade-3 and up, it says:

The output of the cascade is a (potentially empty) sorted list of declared values for each property on each element.

But the top of the cascade section contradicts that, and seems more accurate to me (emphasis added):

The cascade takes an unordered list of declared values for a given property on a given element, sorts them by their declaration’s precedence as determined below, and outputs a single cascaded value.

Am I missing something (/cc @fantasai)? This has been in every level of the spec going back 9 years, so now I don't trust my reading…
@mirisuzanne
Copy link
Contributor Author

After discussing with Tab, I think it's just an editorial issue. Using the term 'output' in both contexts is maybe a bit confusing. The result of the cascade is a sorted list of declared values based on precedence. If not empty, the top of that list is the single cascaded value.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
css-cascade-3 css-cascade-4 Current Work css-cascade-5 css-cascade-6 editorial
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@mirisuzanne