csswg-drafts/css-variables/Overview.src.html at a6f084f8690b0386a218dd5b8fc3c0b4f5de0ab5 · w3c/csswg-drafts · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
<!DOCTYPE html>
<html lang="en">
<head profile="http://www.w3.org/2006/03/hcard">
	<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
	<title>CSS Variables Module Level 1</title>
	<link rel="stylesheet" type="text/css" href="http://dev.w3.org/csswg/default.css">
	<link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/W3C-[STATUS].css">
	<style>
		pre.idl { border:solid thin; background:#eee; color:#000; padding:0.5em }
		pre.idl :link, pre.idl :visited { color:inherit; background:transparent }
	</style>
</head>

<div class="head">
<!--logo-->

<h1>CSS Variables Module Level 1</h1>

<h2 class="no-num no-toc">[LONGSTATUS] [DATE]</h2>
<dl>
	<dt>This version:
		<dd><a href="[VERSION]">http://dev.w3.org/csswg/css-variables/</a>

	<!--<dt>Latest version:
		<dd><a href="http://www.w3.org/TR/[SHORTNAME]/">http://www.w3.org/TR/[SHORTNAME]/</a>-->

	<dt>Editor's draft:
		<dd><a href="http://dev.w3.org/csswg/css-variables/">http://dev.w3.org/csswg/css-variables/</var></a>

	<dt>Editors:
		<dd class="vcard"><span class="fn">Luke Macpherson</span>,
			<span class="org">Google, Inc.</span>,
			<span class="email">macpherson@google.com</span>
		<dd class=vcard>
			<a href="http://xanthir.com/contact/" rel=url>
				<span class=fn>Tab Atkins Jr.</span>,
			</a>
			<span class=org>Google, Inc.</span>
</dl>

<!--copyright-->

<hr title="Separator for header">
</div>

<h2 class="no-num no-toc" id="abstract">Abstract</h2>

	<p>CSS is a language for describing the rendering of structured documents (such as HTML and XML) on screen, on paper,  in speech, etc. This module contains the features of CSS level&nbsp;3 relating to variables. It includes and extends the functionality of CSS level&nbsp;2 [[!CSS21]], which builds on CSS level&nbsp;1 [[CSS1]]. The main extensions compared to level&nbsp;2 are the introduction of the variable as a new primitive value type that is accepted by all properties.

<h2 class="no-num no-toc" id="status">Status of this document</h2>

<!--status-->


<h2 class="no-num no-toc" id="contents">Table of contents</h2>

<!--toc-->

<h2 id="intro">
Introduction</h2>

	<p><em>This section is not normative.</em></p>

	<p>Large documents or applications (and even small ones) can contain quite a bit of CSS.  Many of the values in the CSS file will be duplicate data; for example, a site may establish a color scheme and reuse three or four colors throughout the site.  Altering this data can be difficult and error-prone, since it's scattered throughout the CSS file (and possibly across multiple files), and may not be amenable to Find-and-Replace.</p>

	<p>This module introduces a family of custom user-defined properties known collectively as <i>data properties</i>, which allow an author to assign arbitrary values to a property with an author-chosen name, and then use those values in other properties elsewhere in the document.  This makes it easier to read large files, as seemingly-arbitrary values now have informative names, and makes editting such files much easier and less error-prone, as one only has to change the value once, at the variable definition site, and the change will propagate to all uses of that variable automatically.</p>

<h3 id="placement">
Module Interactions</h3>

	<p>This module defines a new type of primitive value, the <i>variable</i>, which is accepted by all properties.</p>

<h3 id="values">
Values</h3>

	<p>This specification follows the
	<a href="http://www.w3.org/TR/CSS21/about.html#property-defs">CSS property
	definition conventions</a> from [[!CSS21]]. Value types not defined in
	this specification are defined in CSS Level 2 Revision 1 [[!CSS21]].
	Other CSS modules may expand the definitions of these value types: for
	example [[CSS3COLOR]], when combined with this module, expands the
	definition of the &lt;color&gt; value type as used in this specification.</p>

<h2 id="defining-variables">
Defining Variables With Data Properties</h2>

	<p>This specification defines an open-ended set of properties called <i>data properties</i>, which are used to define <i>variables</i>.</p>

	<table class='propdef'>
		<tr>
			<th>Name:</th>
			<td><dfn id='data-property' title='data property|data properties'>data-*</dfn>
		<tr>
			<th>Values:
			<td>see prose
		<tr>
			<th>Initial:
			<td>invalid (a keyword, but see prose)
		<tr>
			<th>Applies To:
			<td>all elements
		<tr>
			<th>Inherited:
			<td>yes
		<tr>
			<th>Computed Value:
			<td>specified value with variables substituted (but see prose for "invalid variables")
		<tr>
			<th>Media:
			<td>all
	</table>

	<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>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>

	<div class='example'>
		<p>For example, even though this spec doesn't define a ''data-inherit()'' function, that name is reserved by default and cannot be used.  Similarly, the ''data()'' function <em>is</em> defined by this spec, so any use of it must match the definition in the spec.  The following property declarations are thus invalid:</p>

		<pre>
:root {
  data-foo: data-inherit(bar); /* Use of reserved, but undefined, function. */
  data-foo: data(bar, baz, qux); /* Invalid use of data() function. */
}</pre>
	</div>

	<p>For each <i>data property</i>, there is an associated variable with the same name save for the "data-" prefix.  For example, a data property named "data-foo" is associated with the variable named "foo".  See the next chapter for details on how to use variables.</p>

	<div class=example>
		<p>This style rule:</p>

		<pre>
:root {
  data-header-color: #06c;
}</pre>

		<p>declares a <i>data property</i> named "data-header-color" on the root element, and assigns to it the value "#06c".  This property is then inherited to the elements in the rest of the document.  Its value can be referenced via the "header-color" variable:

		<pre>h1 { background-color: data(header-color); }</pre>

		<p>The preceding rule is equivalent to writing ''background-color: #06c;'', except that the variable name makes the origin of the color clearer, and if ''data(header-color)'' is used on other elements in the document, all of the uses can be updated at once by changing the 'data-header-color' property on the root element.</p>
	</div>

	<p>Data properties are ordinary properties, so they can be declared on any element, are resolved with the normal inheritance and cascade rules, can be made conditional with ''@media'' and other conditional rules, can be used in HTML's <code>style</code> attribute, can be read or set using the CSSOM, etc..</p>

	<div class='example'>
		<p>If a <i>data property</i> is declared multiple times, the standard cascade rules help resolve it.  Variables always draw from the computed value of the associated data property on the same element:</p>

		<pre>
:root { data-color: blue; }
div { data-color: green; }
#alert { data-color: red; }
* { color: data(color); }

&lt;p>I inherited blue from the root element!&lt;/p>
&lt;div>I got green set directly on me!&lt;/div>
&lt;div id='alert'>
  While I got red set directly on me!
  &lt;p>I'm red too, because of inheritance!&lt;/p>
&lt;/div></pre>
	</div>

	<p><i>Data properties</i> may use variables in their own values to build up composite variables.  This can create cyclic dependencies where two or more <i>data prope
8000
rties</i> each attempt to use the variable that the other defines; doing so makes all the <i>data properties</i> involved in the cycle compute to their initial value (which is a guaranteed-invalid value).</p>

	<div class='example'>
		<p>This example shows a data property safely using a variable:</p>

		<pre>
:root {
	data-main-color: #c06;
	data-accent-background: linear-gradient(to top, data(main-color), white);
}</pre>

		<p>The 'data-accent-background' property will automatically update when the 'data-main-color' property is changed.</p>
	</div>

	<div class='example invalid-example'>
		<p>On the other hand, this example shows an invalid instance of variables depending on each other:</p>

		<pre>
:root {
	data-one: calc(data(two) + 20px);
	data-two: calc(data(one) - 20px);
}</pre>

		<p>Both 'data-one' and 'data-two' now define <i>invalid variables</i> rather than lengths.</p>
	</div>

	<p>It is important to note that <i>data properties</i> resolve any <i>variables</i> in their values at computed-value time, which occurs <em>before</em> the value is inherited.  In general, cyclic dependencies occur only when multiple data properties on the same element refer to each other; data properties defined on elements higher in the element tree can never cause a cyclic reference with properties defined on elements lower in the element tree.</p>

	<div class='example'>
		<p>For example, given the following structure, these data properties are <strong>not</strong> cyclic, and all define valid variables:</p>

		<pre>
&lt;one>&lt;two>&lt;three />&lt;/two>&lt;/one>
one   { data-foo: 10px; }
two   { data-bar: calc(data(foo) + 10px); }
three { data-foo: calc(data(bar) + 10px); }</pre>

		<p>The &lt;one> element defines a value for 'data-foo'.  The &lt;two> element inherits this value, and additionally assigns a value to 'data-bar' using the ''foo'' variable.  Finally, the &lt;three> element inherits the 'data-bar' value <em>after</em> variable substitution (in other words, it sees the value ''calc(10px + 10px)''), and then redefines 'data-foo' in terms of that value.  Since the value it inherited for 'data-bar' no longer contains a reference to the 'data-foo' property defined on &lt;one>, defining 'data-foo' using the ''data(bar)'' variable is not cyclic, and actually defines a value that will eventually (when referenced as a variable in a normal property) resolve to ''30px''.</p>
	</div>

	<p>The initial value of a <i>data property</i> is a special invalid value which makes the associated variable an <i>invalid variable</i>.  This is represented by the keyword ''invalid'', but that keyword has no special meaning in itself, and is valid if set explicitly in a data property.</p>

	<div class='example'>
		<pre>
&lt;div>
  &lt;p>Sample text&lt;/p>
&lt;/div>
&lt;style>
p { data-foo: invalid; }
div,p { font-family: data(foo); }
&lt;/style></pre>

		<p>In this example, the "foo" variable is an <i>invalid variable</i> at the time the DIV element references it, because the 'data-foo' property still has its initial value.  This causes the DIV's 'font-family' property to compute to the initial value for 'font-family'.</p>

		<p>On the other hand, the P element defines an explicit value for the 'data-foo' property.  Its 'font-family' property thus references a font named "invalid".</p>
	</div>


<h2 id='using-variables'>
Using Variables: the data() function</h2>

	<p>A <dfn>variable</dfn> allows the value of a <i>data property</i> on an element to be substituted into another property on the element.  Variables are used with the ''data()'' function, taking the name of a variable and returning the value of the associated data property.  The syntax of the ''data()'' function is:</p>

	<pre><dfn id='type-variable' title="variable|variables">&lt;variable></dfn> = data( IDENT )</pre>

	<p>The ''data()'' function references the <i>data property</i> with the name obtained by prepending "data-" to the function's argument.  <span class='note'>Note that all possible <i>data properties</i> exist; if one with the given name has not yet been defined in the document, it simply takes its initial value.</span>  When a property resolves its computed value, a ''data()'' function is replaced by the value of the referenced <i>data property</i>.</p>

	<p>A variable can be used anywhere a value is expected in CSS.  Variables can not be used as property names, selectors, or anything else besides property values - doing so either produces an invalid value or, in some situations like the attribute value of an attribute selector, a valid value that nonetheless has no relation to the variable of that name.</p>

	<p>A variable is substituted for its value in the property value at computed-value time.  If a declaration, once all variables are substituted in, is invalid, the declaration is <i>invalid at computed-value time</i>.</p>

	<div class='example'>
		<p>For example, the following usage is fine from a syntax standpoint, but results in nonsense when the variable is substituted in:</p>

		<pre>
:root { data-looks-valid: 20px; }
p { background-color: data(looks-valid); }</pre>

		<p>Since ''20px'' is an invalid value for 'background-color', this instance of the property computes to 'transparent' (the initial value for 'background-color') instead.</p>
	</div>

<h3 id='using-invalid-variables'>
Using Invalid Variables</h3>

	<p>When a data property has its initial value, a ''data()'' function referencing that property represents an <dfn title="invalid variable|invalid variables">invalid variable</dfn>.  Using an <i>invalid variable</i> in a property value makes the declaration <i>invalid at computed-value time</i>.</p>

	<p>A declaration that is <dfn>invalid at computed-value time</dfn> results from either using an <i>invalid variable</i> in a property value, or using a valid variable that produces an invalid declaration when it is substituted in.  When this happens, the declaration must compute to the property's initial value.</p>

	<div class='example'>
		<p>For example, in the following code:</p>

		<pre>
:root { data-not-a-color: 20px; }
p { background-color: red; }
p { background-color: data(not-a-color); }</pre>

		<p>the &lt;p> elements will have transparent backgrounds (the initial value for 'background-color'), rather than red backgrounds.  The same would happen if the variable itself was invalid.</p>

		<p>Note the difference between this and what happens if the author had just written ''background-color: 20px'' directly in their stylesheet - that would be a normal syntax error, which would cause the rule to be discarded, so the ''background-color: red'' rule would be used instead.</p>
	</div>

	<p class='note'>The <i>invalid at computed-value time</i> concept exists because variables can't "fail early" like other syntax errors can, so by the time the user agent realizes a property value is invalid, it's already thrown away the other cascaded values.  I think ''attr()'' needs to rely on it as well, as its behavior is almost identical to variables.</p>

<h2 id='cssom'>
CSSOM</h2>

	<p><i>Data properties</i> are ordinary properties, and can be read or modified using all of the existing CSSOM APIs for reading or modifying properties.</p>

	<p>The specification extends the IDL definitions in the CSSOM spec to represent the use of the ''data()'' function.</p>

<h3 id='cssom-cssvariable'>
Interface CSSVariableComponentValue</h3>

	<p>The CSSVariableComponentValue interface represents a use of the ''data()'' function.</p>

	<dl>
		<dt>IDL Definition</dt>
		<dd>
			<pre class='idl'>
[NoInterfaceObject] interface CSSVariableComponentValue {
           attribute DOMString variableName;
  readonly attribute any variableValue;
}</pre>
		</dd>

		<dt>Attributes</dt>
		<dd>
			<dl>
				<dt><code>variableName</code> of type <code>DOMString</code></dt>
				<dd>This attribute represents the argument to the function.  Changing this attribute changes the <i>data property</i> being referred to.</dd>

				<dt><code>variableValue</code> of type <code>any</code>, readonly</dt>
				<dd>This attribute represents the value of the <i>data property</i> the function is referencing.</dd>
			</dl>
		</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>

<h3 id="conventions">
Document Conventions</h3>

	<p>Conformance requirements are expressed with a combination of
	descriptive assertions and RFC 2119 terminology. The key words “MUST”,
	“MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”,
	“RECOMMENDED”, “MAY”, and “OPTIONAL” in the normative parts of this
	document are to be interpreted as described in RFC 2119.
	However, for readability, these words do not appear in all uppercase
	letters in this specification.

	<p>All of the text of this specification is normative except sections
	explicitly marked as non-normative, examples, and notes. [[!RFC2119]]</p>

	<p>Examples in this specification are introduced with the words “for example”
	or are set apart from the normative text with <code>class="example"</code>,
	like this:

	<div class="example">
		<p>This is an example of an informative example.</p>
	</div>

	<p>Informative notes begin with the word “Note” and are set apart from the
	normative text with <code>class="note"</code>, like this:

	<p class="note">Note, this is an informative note.</p>

<h3 id="conformance-classes">
Conformance Classes</h3>

	<p>Conformance to CSS Variables Module
	is defined for three conformance classes:
	<dl>
		<dt><dfn title="style sheet!!as conformance class">style sheet</dfn>
			<dd>A <a href="http://www.w3.org/TR/CSS21/conform.html#style-sheet">CSS
			style sheet</a>.
		<dt><dfn>renderer</dfn></dt>
			<dd>A <a href="http://www.w3.org/TR/CSS21/conform.html#user-agent">UA</a>
			that interprets the semantics of a style sheet and renders
			documents that use them.
		<dt><dfn id="authoring-tool">authoring tool</dfn></dt>
			<dd>A <a href="http://www.w3.org/TR/CSS21/conform.html#user-agent">UA</a>
			that writes a style sheet.
	</dl>

	<p>A style sheet is conformant to CSS Variables Module
	if all of its declarations that use properties defined in this module
	have values that are valid according to the generic CSS grammar and the
	individual grammars of each property as given in this module.

	<p>A renderer is conformant to CSS Variables Module
	if, in addition to interpreting the style sheet as defined by the
	appropriate specifications, it supports all the features defined
	by CSS Variables Module by parsing them correctly
	and rendering the document accordingly. However, the inability of a
	UA to correctly render a document due to limitations of the device
	does not make the UA non-conformant. (For example, a UA is not
	required to render color on a monochrome monitor.)

	<p>An authoring tool is conformant to CSS Variables Module
	if it writes style sheets that are syntactically correct according to the
	generic CSS grammar and the individual grammars of each feature in
	this module, and meet all other conformance requirements of style sheets
	as described in this module.

<h3 id="partial">
Partial Implementations</h3>

	<p>So that authors can exploit the forward-compatible parsing rules to
	assign fallback values, CSS renderers <strong>must</strong>
	treat as invalid (and <a href="http://www.w3.org/TR/CSS21/conform.html#ignore">ignore
	as appropriate</a>) any at-rules, properties, property values, keywords,
	and other syntactic constructs for which they have no usable level of
	support. In particular, user agents <strong>must not</strong> selectively
	ignore unsupported component values and honor supported values in a single
	multi-value property declaration: if any value is considered invalid
	(as unsupported values must be), CSS requires that the entire declaration
	be ignored.</p>

<h3 id="experimental">
Experimental Implementations</h3>

	<p>To avoid clashes with future CSS features, the CSS2.1 specification
	syntax</a> for proprietary and experimental extensions to CSS.

	<p>Prior to a specification reaching the Candidate Recommendation stage
	in the W3C process, all implementations of a CSS feature are considered
	experimental. The CSS Working Group recommends that implementations
	use a vendor-prefixed syntax for such features, including those in
	W3C Working Drafts. This avoids incompatibilities with future changes
	in the draft.
	</p>

<h3 id="testing">Non-Experimental Implementations</h3>

	<p>Once a specification reaches the Candidate Recommendation stage,
	non-experimental implementations are possible, and implementors should
	release an unprefixed implementation of any CR-level feature they
	can demonstrate to be correctly implemented according to spec.

	<p>To establish and maintain the interoperability of CSS across
	implementations, the CSS Working Group requests that non-experimental
	CSS renderers submit an implementation report (and, if necessary, the
	testcases used for that implementation report) to the W3C before
	releasing an unprefixed implementation of any CSS features. Testcases
	submitted to W3C are subject to review and correction by the CSS
	Working Group.

	<p>Further information on submitting testcases and implementation reports
	can be found from on the CSS Working Group's website at
	<a href="http://www.w3.org/Style/CSS/Test/">http://www.w3.org/Style/CSS/Test/</a>.
	Questions should be directed to the
	<a href="http://lists.w3.org/Archives/Public/public-css-testsuite">public-css-testsuite@w3.org</a>
	mailing list.

<h3 id="cr-exit-criteria">
CR Exit Criteria</h3>

	<p>
	For this specification to be advanced to Proposed Recommendation,
	there must be at least two independent, interoperable implementations
	of each feature. Each feature may be implemented by a different set of
	products, there is no requirement that all features be implemented by
	a single product. For the purposes of this criterion, we define the
	following terms:

	<dl>
		<dt>independent <dd>each implementation must be developed by a
		different party and cannot share, reuse, or derive from code
		used by another qualifying implementation. Sections of code that
		have no bearing on the implementation of this specification are
		exempt from this requirement.

		<dt>interoperable <dd>passing the respective test case(s) in the
		official CSS test suite, or, if the implementation is not a Web
		browser, an equivalent test. Every relevant test in the test
		suite should have an equivalent test created if such a user
		agent (UA) is to be used to claim interoperability. In addition
		if such a UA is to be used to claim interoperability, then there
		must one or more additional UAs which can also pass those
		equivalent tests in the same way for the purpose of
		interoperability. The equivalent tests must be made publicly
		available for the purposes of peer review.

		<dt>implementation <dd>a user agent which:

		<ol class=inline>
			<li>implements the specification.

			<li>is available to the general public. The implementation may
			be a shipping product or other publicly available version
			(i.e., beta version, preview release, or “nightly build”).
			Non-shipping product releases must have implemented the
			feature(s) for a period of at least one month in order to
			demonstrate stability.

			<li>is not experimental (i.e., a version specifically designed
			to pass the test suite and is not intended for normal usage
			going forward).
		</ol>
	</dl>

	<p>The specification will remain Candidate Recommendation for at least
	six months.

<h2 class=no-num id="acknowledgments">Acknowledgments</h2>

	<p>Thanks to Daniel Glazman and Dave Hyatt for writing the original Variables draft in 2008.  Thanks to many WG members for keeping the idea of variables alive through the years.</p>

<h2 class=no-num id="references">References</h2>


<h3 class="no-num" id="normative-references">Normative references</h3>
<!--normative-->

<h3 class="no-num" id="other-references">Other references</h3>
<!--informative-->

<h2 class="no-num" id="index">Index</h2>
<!--index-->


<h2 class="no-num" id="property-index">Property index</h2>
<!-- properties -->
</body>
</html>
<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-declaration:"~/SGML/HTML4.decl"
sgml-default-doctype-name:"html"
sgml-minimize-attributes:t
sgml-nofill-elements:("pre" "style" "br")
sgml-live-element-indicator:t
sgml-omittag:nil
sgml-shorttag:nil
sgml-namecase-general:t
sgml-general-insert-case:lower
sgml-always-quote-attributes:t
sgml-indent-step:nil
sgml-indent-data:t
sgml-parent-document:nil
sgml-exposed-tags:nil
sgml-local-catalogs:nil
sgml-local-ecat-files:nil
End:
-->