- From: <bugzilla@jessica.w3.org>
- Date: Wed, 02 Jun 2010 03:35:44 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9828 Summary: Update "Embedding custom non-visible data" with guidance for library authors to avoid naming collisions Product: HTML WG Version: unspecified Platform: All URL: http://dev.w3.org/html5/spec/elements.html#embedding-c ustom-non-visible-data OS/Version: All Status: NEW Severity: normal Priority: P2 Component: HTML5 spec (editor: Ian Hickson) AssignedTo: ian@hixie.ch ReportedBy: adrianba@microsoft.com QAContact: public-html-bugzilla@w3.org CC: mike@w3.org, public-html@w3.org Based on the conversation between Tony and Jonas at: http://lists.w3.org/Archives/Public/public-html/2010May/0034.html Suggest that the text at the end of the section "Embedding custom non-visible data" be changed to: JavaScript libraries may use the custom data attributes, as they are considered to be part of the page on which they are used. Authors of libraries that are reused by many authors are encouraged to include their name in the attribute names, to reduce the risk of clashes. Library authors are also encouraged to make their name customizable by the page author in order to resolve clashes between libraries (including different versions of the same library). For example, a library called "DoQuery" could use attribute names like data-doquery-range, and a library called "jJo" could use attributes names like data-jjo-range. The “jJo” library could also provide clash resolution through an API call like jjo.setDataPrefix("jjo2"), after which the previous example would change to data-jjo2-range. [The last sentence of each paragraph is new.] -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Wednesday, 2 June 2010 03:35:46 UTC