- From: <bugzilla@jessica.w3.org>
- Date: Tue, 18 Dec 2012 19:55:35 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=18669
Ian 'Hixie' Hickson <ian@hixie.ch> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |annevk@annevk.nl,
| |hsivonen@iki.fi,
| |jgraham@opera.com,
| |jonas@sicking.cc,
| |tantek@cs.stanford.edu
--- Comment #8 from Ian 'Hixie' Hickson <ian@hixie.ch> ---
I'd be fine with not using an attribute if we have some other solution. My
concern is that people will abandon the use of semantic HTML in favour of Web
components, in much the same way that they used <font> or <div style="">s. This
hurts accessibility, it hurts search engines, it hurts maintainability, and it
hurts backwards-compatibility (graceful degradation). I would like to avoid
this by requiring that authors use regular HTML elements that they then
_augment_ using Web components.
One way to do that is an is="" attribute on creation. Another is new syntax,
e.g.:
<select/map>
...where "select" is the HTML semantic, and "map" is the component. (This would
parse as <select map=""> in legacy UAs, but in new UAs we could make it
something special that doesn't use attributes.)
I understand that whatever we do, people will end up doing stupid things like
<div/textfield> instead of extending <textarea> or <input>, or whatever. People
will always get it wrong. But please please please let's at least make it
possible to do it right and let's encourage it.
(Note that in the video above, the presenter says she wants to be able to
change the binding live. She calls it "absolutely crucial". :-) )
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 18 December 2012 19:55:37 UTC