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

[compositing-1] [compositing-2] Use bikeshed dfns for compositing modes #380

Closed
Manishearth opened this issue Oct 15, 2019 · 6 comments · Fixed by #381
Closed

[compositing-1] [compositing-2] Use bikeshed dfns for compositing modes #380

Manishearth opened this issue Oct 15, 2019 · 6 comments · Fixed by #381

Comments

@Manishearth
Copy link
Member

Manishearth commented Oct 15, 2019

Currently all the compositing modes use manual <h4 id="porterduffcompositingoperators_foo"> + <a href=#porterduffcompositingoperators_foo> for cross-linking.

We should use Bikeshed <dfn> tags instead, which means that bikeshed-data can pick it up and other specs can easily normatively reference them and have the correct version (TR vs draft) appear in the "references" section.

@Manishearth Manishearth changed the title [compositing-1] [compositing-2] [compositing-1] [compositing-2] Use bikeshed dfns for source-over, lighter, etc Oct 15, 2019
@Manishearth Manishearth changed the title [compositing-1] [compositing-2] Use bikeshed dfns for source-over, lighter, etc [compositing-1] [compositing-2] Use bikeshed dfns for compositing modes Oct 15, 2019
@Manishearth
Copy link
Member Author

cc @rcabanier

@dirkschulze
Copy link
Contributor

@Manishearth The current editor is @chrishtr. Not sure if "bikeshedding" is on the priority list right now :)

@Manishearth
Copy link
Member Author

Oh, sure, Rik's the one who added the references to the XR spec so I thought I'd notify him. It's not a big deal, and I'm planning on fixing this myself, just needed to be sure that this would be okay.

@AmeliaBR
Copy link

If you make a PR with the necessary markup fixes, it makes sense to get this into the Editor's Drafts, which should be enough to get auto-linking working from other specs. I'm not sure whether it would be worth a republication of the TR version, though.

@Manishearth
Copy link
Member Author

Yeah, that makes sense.

@Manishearth
Copy link
Member Author

#381

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

Successfully merging a pull request may close this issue.

3 participants