- From: Tab Atkins Jr.. via cvs-syncmail <cvsmail@w3.org>
- Date: Thu, 10 Nov 2011 22:38:28 +0000
- To: public-css-commits@w3.org
Update of /sources/public/csswg/css-variables
In directory hutz:/tmp/cvs-serv25462
Modified Files:
Overview.html
Log Message:
Argh, forgot to regen.
Index: Overview.html
===================================================================
RCS file: /sources/public/csswg/css-variables/Overview.html,v
retrieving revision 1.27
retrieving revision 1.28
diff -u -d -r1.27 -r1.28
--- Overview.html 10 Nov 2011 22:31:31 -0000 1.27
+++ Overview.html 10 Nov 2011 22:38:26 -0000 1.28
@@ -145,6 +145,10 @@
<ul class=toc>
<li><a href="#cssom-cssvariable"><span class=secno>4.1. </span>
Interface CSSVariableComponentValue</a>
+
+ <li><a href="#cssstyledeclaration-interface"><span class=secno>4.2.
+ </span> Additions to the <code>CSSStyleDeclaration</code> Interface</a>
+
</ul>
<li><a href="#conformance"><span class=secno>5. </span> Conformance</a>
@@ -616,6 +620,17 @@
</dl>
</dl>
+ <h3 id=cssstyledeclaration-interface><span class=secno>4.2. </span>
+ Additions to the <code>CSSStyleDeclaration</code> Interface</h3>
+
+ <p class=issue>The set of data properties is open-ended, so I'm not sure
+ how best to represent this. I'd like to both expose the current set of
+ properties with a non-initial value and allow setting of arbitrary
+ properties. The most natural way seems to be to first, set up a getter
+ behavior on the interface somehow that deals with data properties, and
+ second, set up a <code>data</code> map that exposes the data properties
+ that aren't set to their initial value.
+
<h2 id=conformance><span class=secno>5. </span> Conformance</h2>
<h3 id=conventions><span class=secno>5.1. </span> Document Conventions</h3>
Received on Thursday, 10 November 2011 22:38:29 UTC