- From: <bugzilla@wiggum.w3.org>
- Date: Thu, 26 Nov 2009 02:48:26 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8381
Summary: I greatly appreciate the addition of custom attribute
values, but I take strong exception to the particular
notation. In reality, HTML 5 is providing just one
attribute named "data," which is quite acceptale because
attribute values may be structured. W
Product: HTML WG
Version: unspecified
Platform: Other
URL: http://www.whatwg.org/specs/web-apps/current-
work/#embedding-custom-non-visible-data
OS/Version: other
Status: NEW
Severity: normal
Priority: P3
Component: HTML5 spec bugs
AssignedTo: dave.null@w3.org
ReportedBy: contributor@whatwg.org
QAContact: public-html-bugzilla@w3.org
CC: ian@hixie.ch, mike@w3.org, public-html@w3.org
Section:
http://www.whatwg.org/specs/web-apps/current-work/#embedding-custom-non-visible-data
Comment:
I greatly appreciate the addition of custom attribute values, but I take strong
exception to the particular notation. In reality, HTML 5 is providing just one
attribute named "data," which is quite acceptale because attribute values may
be structured. What's wrong here is the notation. It needlessly forces the
attribute's values to be objects, and it provides ill-advised syntactic sugar
for handling structured data that is already better provided for in javascript.
I recommend dropping the syntactic sugar, dropping the requirement that the
attribute's values be objects, and changing the name from "data" to "u" for
user. The result will be a notation that is simpler, more powerful, easier to
implement, and easier to learn and use -- a quintuple win.
Posted from: 208.103.74.169
--
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Thursday, 26 November 2009 02:48:28 UTC