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
Comments
cc @rcabanier |
@Manishearth The current editor is @chrishtr. Not sure if "bikeshedding" is on the priority list right now :) |
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. |
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. |
Yeah, that makes sense. |
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 thatbikeshed-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.The text was updated successfully, but these errors were encountered: