- From: Tab Atkins Jr.. via cvs-syncmail <cvsmail@w3.org>
- Date: Thu, 10 Nov 2011 22:38:13 +0000
- To: public-css-commits@w3.org
Update of /sources/public/csswg/css-variables In directory hutz:/tmp/cvs-serv25422 Modified Files: Overview.src.html Log Message: Added an issue about the necessary extension to CSSStyleDeclaration. Index: Overview.src.html =================================================================== RCS file: /sources/public/csswg/css-variables/Overview.src.html,v retrieving revision 1.26 retrieving revision 1.27 diff -u -d -r1.26 -r1.27 --- Overview.src.html 10 Nov 2011 22:31:31 -0000 1.26 +++ Overview.src.html 10 Nov 2011 22:38:10 -0000 1.27 @@ -300,6 +300,11 @@ </dd> </dl> +<h3 id='cssstyledeclaration-interface'> +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.</p> + <h2 id="conformance"> Conformance</h2>
Received on Thursday, 10 November 2011 22:38:14 UTC