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 12878 - Master pages wanted eagerly
Summary: Master pages wanted eagerly
Status: CLOSED DUPLICATE of bug 12828
Alias: None
Product: HTML WG
Classification: Unclassified
Component: LC1 HTML5 spec (show other bugs)
Version: unspecified
Hardware: Other All
: P3 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-03 06:56 UTC by HTML WG bugbot
Modified: 2011-08-04 05:13 UTC (History)
4 users (show)

See Also:


Attachments

Description HTML WG bugbot 2011-06-03 06:56:31 UTC
public-html-comments posting from: relay20042004@mail.ru
http://www.w3.org/mid/1721109411.20110531134007@mail.ru

May be I missed something while reading drafts of new HTML standard, but I seriously think, there's one feature that HTML really lacks. I'm talking about Master Pages done with pure HTML only. You may object, saying that there are tons of server technologies including SSI, ASP.NET, PHP, at least JavaScript, to accomplish this task.

But there are also applications where these HTML-based Master Pages would be essential. They are the servers which have server scripting turned off or don't have it at all, such as mini web servers, possibly done on the hardware router base.

There is one truth about server-based master pages: each time such a page is loaded the client should download the web site design again and again instead of downloading master page once, caching it and then applying to each content page. Such a waste of traffic!

There may be also some profit from Master Pages on client side when saving downloaded web sites to disk.

I think, there already are great drafts for this technology present - no need to invent something new from scratch. Look at ASP.NET Master Pages for example. There are basic elements:
1. Link to master page in the content page
2. Named content placeholders in the master page
3. Named structures with contents, which correspond to named placeholders in master page

Please reply me about your opinions concerning implementation of this feature.
And please remember - I am at least one user who needs this technology :) I had enough time to think about that.
Comment 1 Paul 2011-06-03 07:12:26 UTC
The whole message is here: http://www.w3.org/Bugs/Public/show_bug.cgi?id=12828
Comment 2 Michael[tm] Smith 2011-06-03 08:21:27 UTC

*** This bug has been marked as a duplicate of bug 12828 ***
Comment 3 Michael[tm] Smith 2011-08-04 05:13:50 UTC
mass-move component to LC1