That's depressing (the comment was not visible when I posted). Good to know though. You might want to wrap the logic in your own getData() method should you really never want to directly expect that there is an html attribute. Something along the lines of (untested):
This way, data could be set on the element as either an attribute or using .data() and you run no risk of expecting either one when you want to read the data back.
Comment
That's depressing (the comment was not visible when I posted). Good to know though. You might want to wrap the logic in your own getData() method should you really never want to directly expect that there is an html attribute. Something along the lines of (untested):
$.fn.getData( function( attr ){
if ( this.attr( 'data-' + attr ) ) {
return this.attr( 'data-' + attr );
}
return this.data( attr );
} );
This way, data could be set on the element as either an attribute or using .data() and you run no risk of expecting either one when you want to read the data back.
Parent comment
Check what Jurriaan wrote above. There are risks with reading with .data()