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/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)
I should check the history of this requirement, but if it's reasonable, I should indeed probably add <frame>, and also probably <embed>.
This dates back to bug 7599. Looks like an oversight. Fixed.
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