- From: <bugzilla@jessica.w3.org>
- Date: Tue, 15 Jan 2013 22:22:12 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=18669 --- Comment #45 from Dimitri Glazkov <dglazkov@chromium.org> --- Summarizing preliminary developer ergonomics analysis of the proposal in https://www.w3.org/Bugs/Public/show_bug.cgi?id=18669#c36: * Two distinct syntaxes for custom elements, while isn’t anything new for HTML, is a usability problem. Opinions on the severity of this problem vary. * The proposal has a strong “either-or” force of slotting libraries into either only providing things that extend existing HTML elements or only providing a set of custom tags. * The “is” syntax is awkward (a thing that’s like a tag name but is an attribute that you can’t change) and more verbose than the custom tag. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Tuesday, 15 January 2013 22:22:13 UTC