Closed Manishearth closed 5 years ago
Can you elaborate more on why the referenced issue means we have to have a lot of anchors?
Bikeshed has the ability to autolink stuff for specs it knows about. It doesn't know about webxr, yet. So I have to manually add an anchor for everything we reference.
Once bikeshed-data is updated we can remove most of the anchors.
Addressed
Also, I didn't check all the links, just spot checked a few, but we can handle those as we catch them if any are broken.
Yeah, links are fine, they'll improve once we have anchors up, and I don't think we need to actually publish a WD of this spec (just keep drafting it on github) so it's no biggie anyway.
I should also set up travis so that we autopublish to GH pages.
I also set up github pages. I didn't make a PR because it would be harder to test without pushing to master.
Btw, I started on input sources in https://github.com/Manishearth/webxr-test-api/tree/inputsource-bikeshed , but never managed to get to it, feel free to pick it up from there if you want. I'll get back to it at some point.
Talking with the WPT group this week they mentioned that they preferred if this was a proper spec, albeit a one that should never be exposed to users.
This is a first pass at converting it to the bikeshed format. I haven't yet gotten to the input parts. We also should figure out how to set up the Travis stuff so that the spec autopublishes.
We need a lot of anchors currently because https://github.com/tabatkins/bikeshed-data/issues/5 hasn't been resolved yet, once it has we can clean up the anchors.
Rendered
cc @NellWaliczek @toji
r? @alcooper91