Skip to content

[css-color][css-color-3] Needs header link to Editor’s Draft #2445

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

Closed
tantek opened this issue Mar 16, 2018 · 2 comments
Closed

[css-color][css-color-3] Needs header link to Editor’s Draft #2445

tantek opened this issue Mar 16, 2018 · 2 comments
Assignees

Comments

@tantek
Copy link
Member

tantek commented Mar 16, 2018

As is common convention in our modern specs, the header section needs a link to the CSS Color Level 3 Editor's draft (however that draft itself needs regenerating, it says "Editor's Draft 7 July 2014" currently).

We need to update the Editor's draft source with a link to the viewable Editor's Draft, and then regenerate the Editor's draft Overview.html.

Labels: css-color-3, Needs Edits

(Originally published at: http://tantek.com/2018/074/b2/css-color-3-needs-link-editor-draft)

@dbaron
Copy link
Member

dbaron commented Mar 16, 2018

If I hadn't already submitted the comments, I would have referenced this issue from Mozilla's comments on the css-color-3 PR.

@svgeesus
Copy link
Contributor

As is common convention in our modern specs, the header section needs a link to the CSS Color Level 3 Editor's draft (however that draft itself needs regenerating, it says "Editor's Draft 7 July 2014" currently).

CSS Color 3 is unfortunately one of the few specs using the old CSS preprocessor that Bert wrote, and which is no longer maintained. That means that regenerating the draft from the .src means running that preprocessor, then fixing up all the things it gets wrong (lots of boilerplate errors, wrong process document link, generates HTML 4.01, several references are incorrect or not in the old, unmaintained references database it uses, etc).

I agree that the build version of the spec needs to be updated, and i will do that.

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