[Bug 12828] Client-side Master pages wanted eagerly

https://www.w3.org/Bugs/Public/show_bug.cgi?id=12828

Erika Doyle Navara <erika.doyle@microsoft.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |erika.doyle@microsoft.com

--- Comment #9 from Erika Doyle Navara <erika.doyle@microsoft.com> ---
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: Rejected
Change Description: No change
Rationale: 

Hi Paul,

If I understand correctly, you are trying to request a resource and have that
resource choose its "parent" content. For example, requesting a top-level page,
article1.htm would automatically cause articlehost.htm to be downloaded which
would host article1 inside of it. Alternatively, some kind of templating model
for hosting the requested top-level resource would need to be available.

There is currently no notion in HTML for a page being able to specify its host,
as you note with regards to frame and iframe. 

Conceptually it sounds plausible to link to an external HTML file as you would
a CSS or JS file, however the binding behavior would be incredibly difficult to
specify and would likely require some kind of templating or content
host-targeting scheme. That is, the content would require a great deal of
knowledge of the hosting environment to make the binding work.

Furthermore, any content page requiring a master page would of necessity need
to make a 2nd http request. In many cases, especially on slow networks, this
could significantly slow down the time to fully render the combined master
content page. For this reason, master pages on the server make a lot of sense,
but would be far less efficient on the client.

There are alternate proposals to build reusable components that in effect
enable content pages to host reusable components, such as articles. The HTML
Components effort, for example, provides a lot of the rich functionality needed
to make this possible. You might be interested in:
http://www.w3.org/2008/webapps/wiki/Component_Model_Use_Cases#Layout_Manager

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Thursday, 14 February 2013 23:32:27 UTC