This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Specification: http://www.whatwg.org/specs/web-apps/current-work/complete/video-conferencing-and-peer-to-peer-communication.html Multipage: http://www.whatwg.org/C#peer-to-peer-connections Complete: http://www.whatwg.org/c#peer-to-peer-connections Comment: EventTarget here would be more useful if linked to http://dev.w3.org/2006/webapi/DOM-Level-3-Events/html/DOM3-Events.html#webidl- events-EventTarget than the triply or quadruply indirect link it is now. Posted from: 190.49.223.196 User agent: Mozilla/5.0 (X11; Linux i686) AppleWebKit/534.30 (KHTML, like Gecko) Chrome/12.0.742.100 Safari/534.30
What would doing this entail? Is there some easy way for me to do it?
I think it either requires using https://bitbucket.org/ms2ger/specification-data (e.g. <code data-anolis-spec=domcore>Document</code>) or figuring out something new that works for everyone. specification-data is now used by DOM, Editing, XMLHttpRequest, and some other specifications.
I'm not going to do this for a while. Patches welcome though.
*** Bug 14484 has been marked as a duplicate of this bug. ***
This bug was cloned to create bug 18318 as part of operation convergence.
*** Bug 10464 has been marked as a duplicate of this bug. ***
I've gone a bit of a different route, which is that in the source document I put some data-x-href="" attributes on the <dfn> elements that point to other specs, in the Dependencies section mainly, and the pipeline just makes the xrefs to that point to the other specs instead. But I still need to actually put in the xrefs everywhere, so not closing yet.
We've added loads of data-x-href. There's still more to be done, but it's good enough for this bug.