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.

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

[css-2020] Should cascade 3 and 4 both be in the snapshot? #5111

Closed
frivoal opened this issue May 26, 2020 · 3 comments
Closed

[css-2020] Should cascade 3 and 4 both be in the snapshot? #5111

frivoal opened this issue May 26, 2020 · 3 comments

Comments

@frivoal
Copy link
Collaborator

frivoal commented May 26, 2020

(Following up form #4715 (comment), as that's a bit of a separate topic from the overall 4715 issue).

In #4715, we agreed to include cascade 4 in the snapshot. Cascade-3 is already there though.

I don't think anything in cascade 3 is wrong, but it is a little confusing to list both as being the official definition.

Should we just drop cascade 3 from the snapshot? Should we move it to a (newly created) section that lists specs that are stable and correct, but retired due to being superseded by newer ones?

That sort of seems useful, to distinguish such specs from other old RECs which are unmaintained and wrong. People should be reading cascade-4, but they're not going to run into problems if they read cascade-3. On the other hand, the same isn't true about reading CSS2.0 instead of CSS2.1.

@frivoal frivoal added the css-2020 The 2020 snapshot label May 26, 2020
@AmeliaBR
Copy link
Contributor

The snapshot already mentions that level 4 supersedes level 3, (just as it mentions that other specs replace certain sections of CSS 2.1):

CSS Cascading and Inheritance Level 4 [CSS-CASCADE-4]
Extends and supersedes [CSS-CASCADE-3], describing 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.

But it would be helpful, at the very least, to edit the entry for level 3 to indicate that it is fully superseded. And maybe to group the two together in the list, so it is easier to see them as a pair.

But dropping fully superseded specs, or creating a separate list of them, makes sense too.

to distinguish such specs from other old RECs which are unmaintained and wrong

That would be the distinction in the W3C process between a “superseded” spec and an “obsolete” one. I don't know if we want to mention obsolete specs at all in the snapshot, though.

@fantasai
Copy link
Collaborator

I think for snapshot purposes, we only need to link to the latest one that qualifies.

@frivoal
Copy link
Collaborator Author

frivoal commented Dec 16, 2020

Done in cfedc27

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants