W3C home > Mailing lists > Public > public-css-commits@w3.org > February 2012

csswg/css-variables Overview.html,1.30,1.31 Overview.src.html,1.29,1.30

From: Tab Atkins Jr.. via cvs-syncmail <cvsmail@w3.org>
Date: Tue, 28 Feb 2012 02:09:10 +0000
To: public-css-commits@w3.org
Message-Id: <E1S2CV4-0006l7-KP@lionel-hutz.w3.org>
Update of /sources/public/csswg/css-variables
In directory hutz:/tmp/cvs-serv25960

Modified Files:
	Overview.html Overview.src.html 
Log Message:
Add issue about naming.

Index: Overview.html
===================================================================
RCS file: /sources/public/csswg/css-variables/Overview.html,v
retrieving revision 1.30
retrieving revision 1.31
diff -u -d -r1.30 -r1.31
--- Overview.html	11 Feb 2012 01:12:49 -0000	1.30
+++ Overview.html	28 Feb 2012 02:09:08 -0000	1.31
@@ -22,14 +22,14 @@
 
    <h1>CSS Variables Module Level 1</h1>
 
-   <h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 11 February
+   <h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 28 February
     2012</h2>
 
    <dl>
     <dt>This version:
 
     <dd><a
-     href="http://www.w3.org/TR/2012/ED-css-variables-20120211/">http://dev.w3.org/csswg/css-variables/</a>
+     href="http://www.w3.org/TR/2012/ED-css-variables-20120228/">http://dev.w3.org/csswg/css-variables/</a>
      <!--<dt>Latest version:
 		<dd><a href="http://www.w3.org/TR/css-variables/">http://www.w3.org/TR/css-variables/</a>-->
      
@@ -285,6 +285,13 @@
    to them beyond the bare minimum that comes from them being valid
    properties.
 
+  <p class=issue>I'm using data-foo for their rough parallel (in terms of
+   being completely user-extensible) with the data-* attributes in HTML.
+   Might another name be better? Suggestions so far are "var-foo", "$foo",
+   and "var(foo)" (the latter two are intended to directly resemble the usage
+   of the variable). Obviously, usage of the variable should match, as
+   "var(foo)" or "$foo" or whatever.
+
   <p>The valid possible values of a data property are almost completely
    unrestricted. A data property can contain anything that is valid according
    to the <code>value</code> production in the <a

Index: Overview.src.html
===================================================================
RCS file: /sources/public/csswg/css-variables/Overview.src.html,v
retrieving revision 1.29
retrieving revision 1.30
diff -u -d -r1.29 -r1.30
--- Overview.src.html	11 Feb 2012 01:12:49 -0000	1.29
+++ Overview.src.html	28 Feb 2012 02:09:08 -0000	1.30
@@ -113,6 +113,8 @@
 
 	<p><em>Any</em> property name starting with the prefix "data-" is a <i>data property</i>.  Data properties are defined to be valid but meaningless as they are meant solely for allowing authors to pass custom data around their page, similar to the <a href="http://www.whatwg.org/specs/web-apps/current-work/multipage/elements.html#embedding-custom-non-visible-data-with-the-data-*-attributes">custom data attributes</a> in HTML.  Other specifications and user agents must not assign a particular meaning to data properties or attach a specific effect to them beyond the bare minimum that comes from them being valid properties.</p>
 
+	<p class='issue'>I'm using data-foo for their rough parallel (in terms of being completely user-extensible) with the data-* attributes in HTML.  Might another name be better?  Suggestions so far are "var-foo", "$foo", and "var(foo)" (the latter two are intended to directly resemble the usage of the variable).  Obviously, usage of the variable should match, as "var(foo)" or "$foo" or whatever.</p>
+
 	<p>The valid possible values of a data property are almost completely unrestricted.  A data property can contain anything that is valid according to the <code>value</code> production in the <a href="http://www.w3.org/TR/CSS2/syndata.html#tokenization">CSS Core Grammar</a>.  The values do not have to correspond to any existing CSS values, as they are not evaluated except to replace variables occuring within them until they are actually referenced in a normal property with a variable.</p>
 
 	<p>This specification reserves the use of all function tokens starting with the prefix "data" within data properties.  Authors must not use any such functions except as defined in this specification or future updates.  If a data property contains such a function, it must match the grammar defined in this specification or future updates; the use of such a function that does not follow the grammar, or that utilizes such a function that is not yet defined, makes the data property invalid and it must be ignored.</p>
Received on Tuesday, 28 February 2012 02:09:12 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:44:50 UTC