This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 23837 - "iframe or object element" also frame element?
Summary: "iframe or object element" also frame element?
Status: RESOLVED FIXED
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-11-15 17:54 UTC by contributor
Modified: 2013-11-22 18:49 UTC (History)
2 users (show)

See Also:

Attachments

Description contributor 2013-11-15 17:54:57 UTC 
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)
Comment 1 Ian 'Hixie' Hickson 2013-11-18 19:18:27 UTC 
I should check the history of this requirement, but if it's reasonable, I should indeed probably add <frame>, and also probably <embed>.
Comment 2 Ian 'Hixie' Hickson 2013-11-22 18:48:26 UTC 
This dates back to bug 7599. Looks like an oversight. Fixed.
Comment 3 contributor 2013-11-22 18:49:09 UTC 
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