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/multipage/embedded-content-1.html Multipage: http://www.whatwg.org/C#embedded-content-1 Complete: http://www.whatwg.org/c#embedded-content-1 Referrer: http://www.whatwg.org/specs/web-apps/current-work/multipage/ Comment: Give "4.7 Embedded content" a stable id Posted from: 58.187.186.41 User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/33.0.1750.58 Safari/537.36 OPR/20.0.1387.30 (Edition Next)
web-platform-tests uses the IDs of sections in the directory structure and has already become out of sync in embedded content. Can we please have a stable id "embedded-content" for this section?
Done. (Why would this section ever be referenced? It's empty, all the normative content is in subsections that can be referenced directly. Those subsections are highly likely to move around, e.g. canvas was in "embedded content" but is now under "scripting", and so on. I would not recommend relying on high-level section structure in the HTML spec.)
Checked in as WHATWG revision r8506. Check-in comment: introduce stable IDs for 'embedded content' sections http://html5.org/tools/web-apps-tracker?from=8505&to=8506
(In reply to Ian 'Hixie' Hickson from comment #2) > Done. Thanks! > (Why would this section ever be referenced? It's empty, all the normative > content is in subsections that can be referenced directly. Those subsections > are highly likely to move around, e.g. canvas was in "embedded content" but > is now under "scripting", and so on. I would not recommend relying on > high-level section structure in the HTML spec.) Perhaps I should have said "pretty id" instead of "stable id". If the spec moves things around web-platform-tests will have to move along with it, for now I just didn't enjoy the "-0" in the path leading up to the tests I'm working on in html/semantics/embedded-content-0/media-elements/
Looks good, I'll proceed to write tests for this case!
Heh, that was meant for another bug :)