|
14 | 14 | </a></p> |
15 | 15 | <h1 class="p-name no-ref" id=title>CSS Syntax Module Level 3</h1> |
16 | 16 | <h2 class="no-num no-toc no-ref heading settled heading" id=subtitle><span class=content>Editor’s Draft, |
17 | | - <span class=dt-updated><span class=value-title title=20131028>28 October 2013</span></span></span></h2> |
| 17 | + <span class=dt-updated><span class=value-title title=20131029>29 October 2013</span></span></span></h2> |
18 | 18 | <div data-fill-with=spec-metadata><dl><dt>This version:<dd><a class=u-url href=http://dev.w3.org/csswg/css-syntax/>http://dev.w3.org/csswg/css-syntax/</a><dt>Latest version:<dd><a href=http://www.w3.org/TR/css-syntax-3/>http://www.w3.org/TR/css-syntax-3/</a><dt>Editor’s Draft:<dd><a href=http://dev.w3.org/csswg/css-syntax/>http://dev.w3.org/csswg/css-syntax/</a><dt>Previous Versions:<dd><a href=http://www.w3.org/TR/2013/WD-css-syntax-3-20130919/ rel=previous>http://www.w3.org/TR/2013/WD-css-syntax-3-20130919/</a> |
19 | 19 | <dt>Feedback:</dt> |
20 | 20 | <dd><a href="mailto:www-style@w3.org?subject=%5Bcss-syntax%5D%20feedback">www-style@w3.org</a> |
@@ -435,14 +435,11 @@ <h3 class="heading settled heading" data-level=3.2 id=input-byte-stream><span cl |
435 | 435 | <p class=note> Note: the <a data-link-type=dfn href=#decode title=decode>decode</a> algorithm lets the byte order mark (BOM) take precedence, |
436 | 436 | hence the usage of the term "fallback" above. |
437 | 437 |
|
438 | | - <p class=issue id=issue-b26a56fd><a class=self-link href=#issue-b26a56fd></a> |
| 438 | + <p class=issue id=issue-ead8fa31><a class=self-link href=#issue-ead8fa31></a> |
439 | 439 | Anne says that steps 3/4 should be an input to this algorithm from the specs that define importing stylesheet, |
440 | 440 | to make the algorithm as a whole cleaner. |
441 | 441 | Perhaps abstract it into the concept of an "environment charset" or something? |
442 | 442 |
|
443 | | - <p class=issue id=issue-ab273e4b><a class=self-link href=#issue-ab273e4b></a> |
444 | | - Should we only take the charset from the referring document if it’s same-origin? |
445 | | - |
446 | 443 |
|
447 | 444 | <h3 class="heading settled heading" data-level=3.3 id=input-preprocessing><span class=secno>3.3 </span><span class=content> |
448 | 445 | Preprocessing the input stream</span><a class=self-link href=#input-preprocessing></a></h3> |
@@ -2741,10 +2738,6 @@ <h2 class="heading settled heading" data-level=5 id=parsing><span class=secno>5 |
2741 | 2738 | a value consisting of a list of component values, |
2742 | 2739 | and an <var>important</var> flag which is initially unset. |
2743 | 2740 |
|
2744 | | - <p class=issue id=issue-5cca2746><a class=self-link href=#issue-5cca2746></a> |
2745 | | - Should we go ahead and generalize the important flag to be a list of bang values? |
2746 | | - Suggested by Zack Weinberg. |
2747 | | - |
2748 | 2741 | <p> Declarations are further categorized as "properties" or "descriptors", |
2749 | 2742 | with the former typically appearing in <a data-link-type=dfn href=#qualified-rule title="qualified rules">qualified rules</a> |
2750 | 2743 | and the latter appearing in <a data-link-type=dfn href=#at-rule title=at-rules>at-rules</a>. |
@@ -4906,15 +4899,8 @@ <h2 class="no-num heading settled" id=issues-index><span class=content>Issues In |
4906 | 4899 | to make the algorithm as a whole cleaner. |
4907 | 4900 | Perhaps abstract it into the concept of an "environment charset" or something? |
4908 | 4901 |
|
4909 | | - <a href=#issue-b26a56fd> ↵ </a><p class=issue> |
4910 | | - Should we only take the charset from the referring document if it’s same-origin? |
4911 | | - |
4912 | | - |
4913 | | -<a href=#issue-ab273e4b> ↵ </a><p class=issue> |
4914 | | - Should we go ahead and generalize the important flag to be a list of bang values? |
4915 | | - Suggested by Zack Weinberg. |
4916 | 4902 |
|
4917 | | -<a href=#issue-5cca2746> ↵ </a><div class=issue> |
| 4903 | +<a href=#issue-ead8fa31> ↵ </a><div class=issue> |
4918 | 4904 | The following notes should probably be translated into normative text in the relevant specs, |
4919 | 4905 | hooking this spec’s terms: |
4920 | 4906 |
|
|
0 commit comments