- From: Juan Carlos Ojeda <juancarlospaco@gmail.com>
- Date: Mon, 9 Jan 2012 17:25:56 -0300
- To: Matthew Wilcox <elvendil@gmail.com>
- Cc: "www-style@w3.org Style" <www-style@w3.org>
Received on Monday, 9 January 2012 20:26:24 UTC
On Mon, Jan 9, 2012 at 4:28 PM, Matthew Wilcox <elvendil@gmail.com> 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? > SVG got <DOCTYPE SVG>, i dunno CSS -- .
Received on Monday, 9 January 2012 20:26:24 UTC