W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2012

Re: [webcomponents] Custom Elements Spec

From: Ian Hickson <ian@hixie.ch>
Date: Fri, 4 May 2012 18:58:05 +0000 (UTC)
To: "Marat Tanalin | tanalin.com" <mtanalin@yandex.ru>
cc: Dimitri Glazkov <dglazkov@chromium.org>, public-webapps <public-webapps@w3.org>
Message-ID: <Pine.LNX.4.64.1205041856480.9926@ps20323.dreamhostps.com>
On Fri, 4 May 2012, Marat Tanalin | tanalin.com wrote:
> 
> Instead, they have _local_ semantics which purpose is known exclusively 
> for document author/scripts and/or consumers of the document. No any 
> "fallbacks" needed here at all.

So what happens in browsers that don't support components? Or in search 
engines or other data analysis tools that are trying to extract the 
semantics from the page?

Having elements with no well-defined semantic meaning is counter to the 
entire philosophy of the Web, IMHO. I strongly disagree that we should be 
even attempting to allow it, let alone optimising for it.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Friday, 4 May 2012 19:08:19 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:52 GMT