This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Hi all. As we all know that, in JSP we have ""include" so that we can include other web page model into current page, which is very beneficial for code reuse and short G2M. But in html, this capability is very weak. Although we have iframe, but we can not prevent it can not be included by a higher class html page.In another hand, iframe can not be compared with div on layout, iframe's size can only be designated by outside, but can not fit the inner content layout and size. What's more, iframe loading in UA is an new document isolated with parent window, which we be a little strict in some scenario, if we can support div with src attribute, it will be better. So in summary, can we let html support include tag similar with JSP or extending div element to support "src" attribute, so we can extend html to a more modeling mode in architecture view.
Sounds like what you're looking for is http://dev.w3.org/html5/spec/single-page.html#dom-iframe-seamless
This bug was cloned to create bug 17875 as part of operation convergence.
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the Editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the Tracker Issue; or you may create a Tracker Issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Accepted Rationale: This is indeed supported through the seamless attribute.
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the Editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the Tracker Issue; or you may create a Tracker Issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy-v2.html Status: Accepted Change Description: https://github.com/w3c/html/commit/9f91cba7dea7f0769ced7215359b015cc498368f Rationale: adopted WHATWG change to provide an explicit example with inclusion