24694 2014-02-17 15:24:29 +0000 Give "4.7 Embedded content" a stable id 2014-02-22 12:01:36 +0000 1 1 1 Unclassified WHATWG HTML unspecified Other other VERIFIED FIXED http://www.whatwg.org/specs/web-apps/current-work/#embedded-content-1 P3 normal Unsorted 1 contributor ian ian mike philipj contributor oldest_to_newest 100759 0 contributor 2014-02-17 15:24:29 +0000 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) 100761 1 philipj 2014-02-17 15:27:14 +0000 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? 101164 2 ian 2014-02-21 22:39:24 +0000 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.) 101165 3 contributor 2014-02-21 22:39:29 +0000 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 101190 4 philipj 2014-02-22 07:18:58 +0000 (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/ 101191 5 philipj 2014-02-22 09:37:25 +0000 Looks good, I'll proceed to write tests for this case! 101193 6 philipj 2014-02-22 12:01:36 +0000 Heh, that was meant for another bug :)