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

Handle "delta" specs in CSS dumps #117

Closed
tidoust opened this issue Aug 13, 2018 · 2 comments
Closed

Handle "delta" specs in CSS dumps #117

tidoust opened this issue Aug 13, 2018 · 2 comments

Comments

@tidoust
Copy link
Member

tidoust commented Aug 13, 2018

Some newer levels of CSS drafts are currently (and temporarily) defined as "delta" specifications. The list includes:

The CSS dumps created in the css folder are meant to convey the contents of the latest level, but in the case of delta specifications, the latest level does not include the definitions of the previous level, which is a pity.

Consider adding a way to delta flag to spec descriptions and to concatenate the definitions of the delta spec with the definitions of the previous level for such specs.

@dontcallmedom
Copy link
Member

@tidoust is this handled by reffy now that we're tracking that state in browser-specs?

@tidoust
Copy link
Member Author

tidoust commented Jun 23, 2020

I believe we can close.

With the "delta" info in browser-specs, CSS extracts created by Reffy are those for the full spec. We could easily switch to a model where Reffy produces extracts both for the full spec and the delta spec (using the leveled shortname to name files, as done for definitions) if that seems useful. Pending requests for such a feature, I suggest we just leave it at that for now.

(Merging the full and delta definitions seems more "risky" in that I'm not sure all delta specs merely extend full specs on which they are based)

@tidoust tidoust closed this as completed Jun 23, 2020
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

2 participants