Setting data() via an object with hyphenated keys create inaccessible data.

[mdawaffe]

If an element's data is set via an object with a hyphenated key, that key becomes inaccessible.

Test case: ​http://jsfiddle.net/V8y7X/

Related and caused by: #9124

[Rick Waldron]

Further reduction: ​http://jsfiddle.net/rwaldron/Azjar/

[john]

Nominating ticket for 1.7 discussion.

[Rick Waldron]

+1, Seems like a bug, should be fixed

[jaubourg]

+1, bug

[timmywil]

+1,

[dmethvin]

+1, OK, so I guess the solution is to take two stabs into the data object, one camelCase and the second camel-case?

[john]

+1, Seems like we should get this in 1.6.2.

[Rick Waldron]

​https://github.com/jquery/jquery/pull/403

[ajpiano]

+1, Buggy mc buggerson

[scottgonzalez]

+1

[rwldrn]

Landing pull request 403. Check for both camelized and hyphenated data property names; Fixes #9301.

More Details:

• ​https://github.com/jquery/jquery/pull/403
• ​http://bugs.jquery.com/ticket/9301 Changeset: 07420566452622f37b01e69bbbdcbeeb5317e065

[Jean-Sébastien Goupil <[email protected]…>]

Related bug added #9700

[anonymous]

I am not sure this is fixed. Or this fixed created more issues.

There is something wrong with .data with using numerical data.

Here is a jsFiddle showing the issue. You can remove the resource and test in the previous version. ​http://jsfiddle.net/UhMxP/

[Rick Waldron]

Can you make a _reduced_ test case?

[Rick Waldron]

Also, per the HTML5 data-* attr spec (which users requested that jQuery follow), hyphenated attributes are accessed by their camel cased equivalent

[Rick Waldron]

This is really bizarre, I just tried to create a test case out of this fiddle:

​http://jsfiddle.net/rwaldron/6L5cs/

...and the tests pass perfectly using the current upstream master codebase.

[Adam Jenkins]

This is not fixed at all....if anything, it's now broken worse.

I wrote a plugin that used simple (string) data keys like .data('gs-offset') that work in jQuery <1.6.2 but not in v1.6.2. When I remove the hyphens on them all and use v1.6.2, they 'work' again, but this creates a horrendous backwards compatibility problem.

This needs to be fixed ASAP.

[Rick Waldron]

Adam, Can you post a link to your plugin's code? That would help be understand what the difference beween our test suite and your real-world use case is so I can narrow down where I've gotten it wrong.

[Adam Jenkins <[email protected]…>]

No need for the plugin, a much simple demonstration will do:

 $(body).data('nohyphen','good').data('has-hypen','bad');
 console.log($(body).data('nohyphen'));
 console.log($(body).data('has-hyphen')); 

[Adam Jenkins <[email protected]…>]

Replying to Adam Jenkins <[email protected]…>:

No need for the plugin, a much simple demonstration will do:

 $(body).data('nohyphen','good').data('has-hypen','bad');
 console.log($(body).data('nohyphen'));
 console.log($(body).data('has-hyphen')); 

I obviously made some a spelling mistake in the above code, should be:

  $(body).data('nohyphen','good').data('has-hyphen','bad');
  console.log($(body).data('nohyphen'));
  console.log($(body).data('has-hyphen')); 

[Adam Jenkins <[email protected]…>]

Replying to Adam Jenkins <[email protected]…>:

Replying to Adam Jenkins <[email protected]…>:

No need for the plugin, a much simple demonstration will do:

 $(body).data('nohyphen','good').data('has-hypen','bad');
 console.log($(body).data('nohyphen'));
 console.log($(body).data('has-hyphen')); 

And this is obviously fine, I must have made another spelling error when testing it out locally....I'll post the plugin code shortly.

I obviously made some a spelling mistake in the above code, should be:

  $(body).data('nohyphen','good').data('has-hyphen','bad');
  console.log($(body).data('nohyphen'));
  console.log($(body).data('has-hyphen')); 

[Rick Waldron]

#9775 is a duplicate of this ticket.

[Rick Waldron]

#9775 is a duplicate of this ticket.

[Rick Waldron]

#9792 is a duplicate of this ticket.

[anonymous]

Hi there,

I just downloaded 1.6.2 and data function is broken. I just made the following test:

​http://jsfiddle.net/Jb8kA/

Omar Diego Vera

[Rick Waldron]

@Omar, yes. thanks.

It will be fixed in the next release. See: ​https://github.com/jquery/jquery/pull/432