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 19:29:19 +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.1205041913550.9926@ps20323.dreamhostps.com>
On Fri, 4 May 2012, Marat Tanalin | tanalin.com wrote:
> >
> > 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?
> Elements with custom tag-names would have EXACTLY SAME semantic (as for 
> core HTML5 semantics) meaning as a common container (SPAN or DIV) with a 
> class. No more and no less.

If it's purely stylistic, then using <div> and not having semantics is 
fine. Stylistic components should just be invoked from the CSS layer.

Components that are not purely stylistic, e,g, things like form controls
or data (tables or graphical), need to have fallback semantics. Those are 
the ones that appear in the markup.

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

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:13:34 UTC