This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Web Components indirectly codifies the notion that hyphen-containing elements are open as extension points and will not be overtaken by the browser in future (minus a small, specific existing list): https://dvcs.w3.org/hg/webcomponents/raw-file/tip/spec/custom/index.html#dfn-custom-element-type This should be made explicit in the HTML specification, and extended to attributes (also with a list of exclusions). This should help stop people from using data-* for standards that build atop HTML.
Robin, do you really think this blocks CR? Or can we wait on this till 5.1?
(In reply to Travis Leithead [MSFT] from comment #1) > Robin, do you really think this blocks CR? Or can we wait on this till 5.1? I don't think it's a long conversation. If it's no we can just drop it, if it's yes it's a small change. So it's "blocking" but it can't really block.
Based on the discussion here: http://lists.w3.org/Archives/Public/public-html/2013Oct/0005.html I think this is a Won't Fix for now. Thoughts?
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the Editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the Tracker Issue; or you may create a Tracker Issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Rejected Change Description: none Rationale: It's a wonderful idea but based on discussion we'll have to wait for its time to come.