W3C home > Mailing lists > Public > public-html@w3.org > July 2007

Re: DI element [Re: html 5 and accessibility issue]

From: Henri Sivonen <hsivonen@iki.fi>
Date: Tue, 3 Jul 2007 13:59:58 +0300
Message-Id: <DECB261F-E510-4073-A0C8-0CEF8B9E79C3@iki.fi>
Cc: "Ian Hickson" <ian@hixie.ch>, "Ben Boyle" <benjamins.boyle@gmail.com>, "Andrew Ramsden" <andrew@irama.org>, "Andrew Sidwell" <takkaria@gmail.com>, aurélien levy <aurelien.levy@free.fr>, public-html@w3.org
To: Charles McCathieNevile <chaals@opera.com>

On Jul 3, 2007, at 12:11, Charles McCathieNevile wrote:

> Because it means they have to write their own microparser to  
> actually interpret those semantics,

Not too much to ask, in my opinion. (Boils down to "programming too  
hard for software developers".)

If HTML5 had <di>, the parsing algorithm (and, by consequence, off- 
the-shelf parsing libraries) would have to add it implicitly or else  
the document tree would still be able to contain the implicitly  
grouped case and which would still require app-level handling by the  
desperate microformat hacker. But if HTML5 did that, the parsing  
algorithm would not be suitable for existing content in the browser  
case as Selectors would match differently all of a sudden.

-- 
Henri Sivonen
hsivonen@iki.fi
http://hsivonen.iki.fi/
Received on Tuesday, 3 July 2007 11:00:23 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:16:02 GMT