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

[META-THEME-COLOR] should become some sort of alias of [HTML]? #252

Closed
domenic opened this issue Mar 17, 2016 · 5 comments
Closed

[META-THEME-COLOR] should become some sort of alias of [HTML]? #252

domenic opened this issue Mar 17, 2016 · 5 comments

Comments

@domenic
Copy link
Collaborator

domenic commented Mar 17, 2016

See https://github.com/whatwg/meta-theme-color

Not sure what the best procedure is here. It seems weird to make it a pure alias since then bibliographies will say things like "[META-THEME-COLOR]. HTML. Living Standard. https://html.spec.whatwg.org/multipage/." Maybe delete it and make everyone fix their breakages?

See also w3c/manifest#431.

@tobie
Copy link
Owner

tobie commented Mar 17, 2016

I think the right way to proceed would be to add "obsoletedBy": ["HTML"] to the to the META-THEME-COLOR entry.

This let's the tools warn editors appropriately (nudge @tabatkins, @halindrome, @marcoscaceres).

This can be done either in the WHATWG resource file or in the Specref WHATWG ref file. Your pick.

@domenic
Copy link
Collaborator Author

domenic commented Mar 17, 2016

Specref sounds better, since that way we can keep the WHATWG resources file to only contain specs.

@tobie
Copy link
Owner

tobie commented Mar 17, 2016

@tabatkins
Copy link
Collaborator

I don't handle obsoletes/obsoletedBy yet, but I've added an issue for it.

(Are the two guaranteed to be mirrors of each other?)

@tobie
Copy link
Owner

tobie commented Mar 18, 2016

(Are the two guaranteed to be mirrors of each other?)

No. I'm not checking this data.

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

No branches or pull requests

3 participants