Skip to content

Commit 4ff7a6e

Browse files
committed
[cssom] note issues regarding retention of cssText in parse error conditions
1 parent 2a584d1 commit 4ff7a6e

2 files changed

Lines changed: 14 additions & 8 deletions

File tree

cssom/Overview.html

Lines changed: 8 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ <h1 id="cssom">CSS Object Model (CSSOM)</h1>
1818

1919
<!-- ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -->
2020

21-
<h2 class="no-num no-toc" id="w3c-doctype">Editor's Draft 2 October 2012</h2>
21+
<h2 class="no-num no-toc" id="w3c-doctype">Editor's Draft 19 October 2012</h2>
2222

2323
<dl>
2424

@@ -83,7 +83,7 @@ <h2 class="no-num no-toc" id="sotd">Status of this Document</h2>
8383
can be found in the
8484
<a href="http://www.w3.org/TR/">W3C technical reports index at http://www.w3.org/TR/.</a></em>
8585

86-
<p class="dontpublish">This is the 2 October 2012 Editor's Draft of CSSOM. Please send comments to
86+
<p class="dontpublish">This is the 19 October 2012 Editor's Draft of CSSOM. Please send comments to
8787
<a href="mailto:www-style@w3.org?subject=%5Bcssom%5D%20">www-style@w3.org</a>
8888
(<a href="http://lists.w3.org/Archives/Public/www-style/">archived</a>)
8989
with <samp>[cssom]</samp> at the start of the subject line.
@@ -1548,6 +1548,9 @@ <h3 id="css-rules"><span class="secno">6.4 </span>CSS Rules</h3>
15481548

15491549
<p>To <dfn id="parse-a-css-rule">parse a CSS rule</dfn> ...</p>
15501550

1551+
<p class="issue">Should a rule be instantiated in OM if there is a parse error? To
1552+
what extent should original (but non-valid) CSS text be captured in cssText?</p>
1553+
15511554
<p>To <dfn id="serialize-a-css-rule">serialize a CSS rule</dfn> depends on the type of CSS rule, as
15521555
follows:</p>
15531556

@@ -1839,10 +1842,10 @@ <h3 id="css-declaration-blocks"><span class="secno">6.5 </span>CSS Declaration B
18391842
ordered. This matters for the
18401843
<code title="dom-CSSStyleDeclaration-item">item()</code> method.</p>
18411844

1845+
<p>To <dfn id="parse-a-css-declaration-block">parse a CSS declaration block</dfn> ...</p>
18421846

1843-
<p class="issue">To
1844-
<dfn id="parse-a-css-declaration-block">parse a CSS declaration block</dfn>
1845-
...</p>
1847+
<p class="issue">What should be captured in the cssText of a declaration block which fails
1848+
to parse?</p>
18461849

18471850
<p>To <dfn id="serialize-a-css-declaration-block">serialize a CSS declaration block</dfn>
18481851
represented by a <code>CSSStyleDeclarations</code> instance named <var>d</var>,

cssom/cssom-source

Lines changed: 6 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1318,6 +1318,9 @@
13181318

13191319
<p>To <dfn>parse a CSS rule</dfn> ...</p>
13201320

1321+
<p class="issue">Should a rule be instantiated in OM if there is a parse error? To
1322+
what extent should original (but non-valid) CSS text be captured in cssText?</p>
1323+
13211324
<p>To <dfn>serialize a CSS rule</dfn> depends on the type of CSS rule, as
13221325
follows:</p>
13231326

@@ -1442,10 +1445,10 @@
14421445
ordered. This matters for the
14431446
<code title="dom-CSSStyleDeclaration-item">item()</code> method.</p>
14441447

1448+
<p>To <dfn id="parse-a-css-declaration-block">parse a CSS declaration block</dfn> ...</p>
14451449

1446-
<p class="issue">To
1447-
<dfn id="parse-a-css-declaration-block">parse a CSS declaration block</dfn>
1448-
...</p>
1450+
<p class="issue">What should be captured in the cssText of a declaration block which fails
1451+
to parse?</p>
14491452

14501453
<p>To <dfn id="serialize-a-css-declaration-block">serialize a CSS declaration block</dfn>
14511454
represented by a <code>CSSStyleDeclarations</code> instance named <var>d</var>,

0 commit comments

Comments
 (0)