- From: <bugzilla@jessica.w3.org>
- Date: Tue, 03 Sep 2013 11:51:53 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=22914
Robin Berjon <robin@w3.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |CR
Status|NEW |RESOLVED
CC| |robin@w3.org
Resolution|--- |WONTFIX
--- Comment #4 from Robin Berjon <robin@w3.org> ---
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: Reflection is indeed specified here. David: the confusion here is
that jQuery's data() is actually something rather different. You can use data-*
attributes to store additional information on the tree, but it's limited to the
sort of stuff you can put in an attribute value. jQuery's data() is used to add
pretty much any kind of data that JS can hold to an element. You can include
things like pointers to another node, or the complete implementation of a
plugin (so that if a plugin instance is handling the element's behaviour, you
can grab the instance and interact with it using data()). It's not the same
thing, and you really couldn't reflect what jQuery does into the DOM (at least
not in a way that could make sense serialised).
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 3 September 2013 11:51:54 UTC