W3C home > Mailing lists > Public > www-style@w3.org > January 2012

Re: A CSS equivalent of HTML's DOCTYPE trigger

From: Anton Prowse <prowse@moonhenge.net>
Date: Mon, 09 Jan 2012 21:36:11 +0100
Message-ID: <4F0B4FBB.3080108@moonhenge.net>
To: www-style@w3.org
CC: Matthew Wilcox <mail@matthewwilcox.com>
On 09/01/2012 20:28, Matthew Wilcox wrote:
> HTML has a useful property whereby the DOCTYPE was hijacked to trigger standards compliant rendering modes.
>
> Some of CSS is sub-optimally implemented from a designer/typographer standpoint and there's not much tht can be done about it by us without breaking backward compatibility.
>
> Has thought been put into an equivalent strategy for CSS? For example, opting into which branch or module we'd like to work?
>
> I bring this up because I think the way typography is handled in CSS is simply fundamentally flawed from a typographers perspective, and un-resquable as is. If we could wind back the clock we could fix it, but we can't. How about we reset the clock? Allowing the author to choose which versions of the spec to adhere to?
>
> That would allow us to, for example, re-write the way that font's are used in CSS, without breaking backward compatibility. User Agents that don't understand the trigger would simply ignore it.
>
> Thoughts?

I think this would be horrible!

If a new inline formatting model is desired, perhaps a new property 
could be introduced which can let authors choose between them?

But way before that, it needs to be established what a new inline 
formatting model would look like.

Cheers,
Anton Prowse
http://dev.moonhenge.net
Received on Monday, 9 January 2012 20:39:19 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:48 GMT