Skip to content

Commit

Permalink
Browse files Browse the repository at this point in the history
[e] (0) Suggest that 'data-*-*' should allow the prefix to be changed…
… in libraries.

Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=9828

git-svn-id: http://svn.whatwg.org/webapps@5469 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information
Hixie committed Sep 23, 2010
1 parent 2dc0187 commit 5f22e66
Show file tree
Hide file tree
Showing 3 changed files with 33 additions and 8 deletions.
14 changes: 11 additions & 3 deletions complete.html
Expand Up @@ -209,7 +209,7 @@

<header class=head id=head><p><a class=logo href=http://www.whatwg.org/ rel=home><img alt=WHATWG height=101 src=/images/logo width=101></a></p>
<hgroup><h1>Web Applications 1.0</h1>
<h2 class="no-num no-toc">Draft Standard &mdash; 10 September 2010</h2>
<h2 class="no-num no-toc">Draft Standard &mdash; 23 September 2010</h2>
</hgroup><p>You can take part in this work. <a href=http://www.whatwg.org/mailing-list>Join the working group's discussion list.</a></p>
<p><strong>Web designers!</strong> We have a <a href=http://blog.whatwg.org/faq/>FAQ</a>, a <a href=http://forums.whatwg.org/>forum</a>, and a <a href=http://www.whatwg.org/mailing-list#help>help mailing list</a> for you!</p>
<!--<p class="impl"><strong>Implementors!</strong> We have a <a href="http://www.whatwg.org/mailing-list#implementors">mailing list</a> for you too!</p>-->
Expand Down Expand Up @@ -9813,13 +9813,21 @@ <h5 id=embedding-custom-non-visible-data><span class=secno>3.2.3.8 </span><dfn>E
attribute">custom data attributes</a>, 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.</p>
in the attribute names, to reduce the risk of clashes. Where it
makes sense, library authors are also encouraged to make the exact
name used in the attribute names customizable, so that libraries
whose authors unknowingly picked the same name can be used on the
same page, and so that multiple versions of a particular library can
be used on the same page even when those versions are not mutually
compatible.</p>

<div class=example>

<p>For example, a library called "DoQuery" could use attribute
names like <code title="">data-doquery-range</code>, and a library
called "jJo" could use attributes names like <code title="">data-jjo-range</code>.</p>
called "jJo" could use attributes names like <code title="">data-jjo-range</code>. The jJo library could also provide
an API to set which prefix to use (e.g. <code title="">J.setDataPrefix('j2')</code>, making the attributes have
names like <code title="">data-j2-range</code>).</p>

</div>

Expand Down
14 changes: 11 additions & 3 deletions index
Expand Up @@ -213,7 +213,7 @@

<header class=head id=head><p><a class=logo href=http://www.whatwg.org/ rel=home><img alt=WHATWG height=101 src=/images/logo width=101></a></p>
<hgroup><h1>HTML5 (including next generation additions still in development)</h1>
<h2 class="no-num no-toc">Draft Standard &mdash; 10 September 2010</h2>
<h2 class="no-num no-toc">Draft Standard &mdash; 23 September 2010</h2>
</hgroup><p>You can take part in this work. <a href=http://www.whatwg.org/mailing-list>Join the working group's discussion list.</a></p>
<p><strong>Web designers!</strong> We have a <a href=http://blog.whatwg.org/faq/>FAQ</a>, a <a href=http://forums.whatwg.org/>forum</a>, and a <a href=http://www.whatwg.org/mailing-list#help>help mailing list</a> for you!</p>
<!--<p class="impl"><strong>Implementors!</strong> We have a <a href="http://www.whatwg.org/mailing-list#implementors">mailing list</a> for you too!</p>-->
Expand Down Expand Up @@ -9790,13 +9790,21 @@ background: transparent"&gt;blue&lt;/span&gt;.&lt;/p&gt;</pre>
attribute">custom data attributes</a>, 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.</p>
in the attribute names, to reduce the risk of clashes. Where it
makes sense, library authors are also encouraged to make the exact
name used in the attribute names customizable, so that libraries
whose authors unknowingly picked the same name can be used on the
same page, and so that multiple versions of a particular library can
be used on the same page even when those versions are not mutually
compatible.</p>

<div class=example>

<p>For example, a library called "DoQuery" could use attribute
names like <code title="">data-doquery-range</code>, and a library
called "jJo" could use attributes names like <code title="">data-jjo-range</code>.</p>
called "jJo" could use attributes names like <code title="">data-jjo-range</code>. The jJo library could also provide
an API to set which prefix to use (e.g. <code title="">J.setDataPrefix('j2')</code>, making the attributes have
names like <code title="">data-j2-range</code>).</p>

</div>

Expand Down
13 changes: 11 additions & 2 deletions source
Expand Up @@ -9978,14 +9978,23 @@ background: transparent">blue&lt;/span>.&lt;/p></pre>
attribute">custom data attributes</span>, 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.</p>
in the attribute names, to reduce the risk of clashes. Where it
makes sense, library authors are also encouraged to make the exact
name used in the attribute names customizable, so that libraries
whose authors unknowingly picked the same name can be used on the
same page, and so that multiple versions of a particular library can
be used on the same page even when those versions are not mutually
compatible.</p>

<div class="example">

<p>For example, a library called "DoQuery" could use attribute
names like <code title="">data-doquery-range</code>, and a library
called "jJo" could use attributes names like <code
title="">data-jjo-range</code>.</p>
title="">data-jjo-range</code>. The jJo library could also provide
an API to set which prefix to use (e.g. <code
title="">J.setDataPrefix('j2')</code>, making the attributes have
names like <code title="">data-j2-range</code>).</p>

</div>

Expand Down

0 comments on commit 5f22e66

Please sign in to comment.