4 ms·
I think that's an interesting point, and certainly a problem that will grow as data attributes become even more widely used. Perhaps there's even use for a lit
by heelhook 14y ago
I think that's an interesting point, and certainly a problem that will grow as data attributes become even more widely used.
Perhaps there's even use for a little database that keeps track of the different data attributes used by different libraries so that authors could easily find out if their name of choice will collide with someone else's, at least as a forewarning to its user about possible incompatibilities.
- rurounijones 14y agoAnother option (Although much more complicated) would be to make the used data attributes configurable in the script. Maximum flexibility for the end-user but a bit of a PITA for library developers.
- matb33 14y agoThis is the way to go, and really not that hard to implement for the library developers
- xaritas 14y agoSome sort of data attribute namespace, which is uniquely identified by a URI, and aliased within the document to shorter version? Might look something like this? dans:chardin="http://heelhook.github.com/chardin.js/ http://heelhook.github.com/chardin.js/ I have a feeling that web community is not ready for something like this, maybe in a few years.