23837 2013-11-15 17:54:57 +0000 "iframe or object element" also frame element? 2013-11-22 18:49:09 +0000 1 1 1 Unclassified WHATWG HTML unspecified Other other RESOLVED FIXED http://www.whatwg.org/specs/web-apps/current-work/#navigate-fragid-step P3 normal Unsorted 1 contributor ian ian mike contributor oldest_to_newest 96373 0 contributor 2013-11-15 17:54:57 +0000 Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/history.html Multipage: http://www.whatwg.org/C#navigate-fragid-step Complete: http://www.whatwg.org/c#navigate-fragid-step Referrer: http://www.whatwg.org/specs/web-apps/current-work/multipage/links.html Comment: "iframe or object element" also frame element? Posted from: 94.234.170.170 User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/31.0.1650.26 Safari/537.36 OPR/18.0.1284.11 (Edition Next) 96442 1 ian 2013-11-18 19:18:27 +0000 I should check the history of this requirement, but if it's reasonable, I should indeed probably add <frame>, and also probably <embed>. 96712 2 ian 2013-11-22 18:48:26 +0000 This dates back to bug 7599. Looks like an oversight. Fixed. 96713 3 contributor 2013-11-22 18:49:09 +0000 Checked in as WHATWG revision r8307. Check-in comment: Fix the rules on what 'Origin' header to use when navigating to a resource in an <iframe>, <object>, <embed>, or <frame> element, so that the latter two are not forgotten. http://html5.org/tools/web-apps-tracker?from=8306&to=8307