W3C home > Mailing lists > Public > www-style@w3.org > August 2005

Re: [css3-ui] Problems with :read-only and :read-write

From: Laurens Holst <lholst@students.cs.uu.nl>
Date: Fri, 05 Aug 2005 00:51:08 +0200
Message-ID: <42F29BDC.9060406@students.cs.uu.nl>
To: www-style@w3.org

Adam Kuehn wrote:
>> You can keep the expressiveness without allowing for the abuse.
> Show me.
Yes, show me, too.

The only way that I can to achieve that see is to disable author-CSS, 
and make sure that website authors can only get their desired style by 
using the correct semantic markup.

But... we have that for many, many years. It is called HTML! In the 
beginning, there was no CSS. Did authors create good semantic sites? No, 
in the contrary, website authors took the control that they wanted and 
started to abuse tables, blockquotes, etcetera for things that they were 
not intended for. Nowadays we refer to that as ‘table-based-layouts’, 
and I am sure that we are all glad to be rid of it.

In other words, if you do not allow the website author to layout his web 
page, things will turn into a mess because they *will* take control 
anyway. And the tables and blockquotes example showed that even without 
CSS, perfect semantic elements can be abused for non-semantic purposes. 
Additionally, if you do allow author-CSS (even just a small subset), 
then a website author will always be able to abuse the system, e.g. by 
applying ‘font-size: xx-large’ to a <p> element instead of using a 
heading <h> element.


~Grauw

-- 
Ushiko-san! Kimi wa doushite, Ushiko-san!!
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Laurens Holst, student, university of Utrecht, the Netherlands.
Website: www.grauw.nl. Backbase employee; www.backbase.com.
Received on Thursday, 4 August 2005 22:51:13 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 27 April 2009 13:54:39 GMT