RE: no-cascade proposition

The benefit is that you could actually do what you want to do easily, predictably and reliably ? Here is how it would work.

Government web site designs their pages and reserves a container in their design for the top banner; *they* author this markup.

Later on, your own markup and CSS will load in that container, the semantics of which guarantee your banner will not interfere with the page - it's a two way problem: they don't want your CSS to mess with their page either - nor that your banner will be affected by their updates.

I really don't see why adding one extra container tag is such a big deal. It certainly is a lot less complex for all the components - HTML and CSS parser, layout engine - and people - web site designer, banner author - involved.

________________________________________
From: Niels Matthijs [niels.matthijs@internetarchitects.be]
Sent: Wednesday, December 24, 2008 4:20 AM
To: Sylvain Galineau; www-style@w3.org
Subject: RE: no-cascade proposition

Sylvain Galineau wrote:

> I like the concept but explicit markup mechanisms are much better here imo.

Hmmm, let me try out an example. Imagine having to create a top banner for all government sites of the country you live in. Each site has its own design, is developed by a different party and has (almost) total autonomy. The only common element is the top banner with a link to the government portal and a language navigation.

So you have to write xhtml and css for the banner, and you have to make sure it shows up correctly in all sites. Problem is that you don't know the css of these sites. Still, it should be possible to implement the top banner everywhere without creating visual inconsistencies

What you deliver is just a piece of xhtml and css, so can anyone explain to me why this piece of code should be separately marked in the actual mark-up? I fail to see the benefit.

Greets,
Niels Matthijs

Received on Sunday, 28 December 2008 17:05:57 UTC