Skip to content

Commit d571fb2

Browse files
committed
[css-syntax-3][editorial] Updated Changes section.
1 parent 30c1c7e commit d571fb2

File tree

1 file changed

+44
-0
lines changed

1 file changed

+44
-0
lines changed

css-syntax-3/Overview.bs

Lines changed: 44 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3780,6 +3780,50 @@ Changes</h2>
37803780

37813781
<em>This section is non-normative.</em>
37823782

3783+
<h3 id="changes-CR-20211224">
3784+
Changes from the 24 December 2021 Candidate Recommendation Draft</h3>
3785+
3786+
The following substantive changes were made:
3787+
3788+
* The definition of [=non-ASCII code point=]
3789+
was restricted to omit some potentially troublesome codepoints.
3790+
(<a href="https://github.com/w3c/csswg-drafts/issues/7129">7129</a>)
3791+
3792+
* Defined the <code>&lt;foo()></code> and <code>&lt;@foo></code> productions.
3793+
(<a href="https://github.com/w3c/csswg-drafts/issues/5728">5728</a>)
3794+
3795+
* Allow nested style rules.
3796+
(<a href="https://github.com/w3c/csswg-drafts/issues/7961#issuecomment-1514955984">7961</a>).
3797+
3798+
* As part of allowing Nesting,
3799+
significantly rewrote the entire parsing section.
3800+
Notably, removed "parse a list of rules" and "parse a list of declarations"
3801+
in favor of "parse a stylesheet's contents" and "parse a block's contents".
3802+
Only additional normative change is that
3803+
semicolons trigger slightly different error-recovery now
3804+
in some contexts,
3805+
so that parsing of things like ''@media'' blocks
3806+
is identical whether they're nested or not.
3807+
(<a href="https://github.com/w3c/csswg-drafts/issues/8834">8834</a>).
3808+
3809+
* Removed the attempt at a <code>&lt;urange></code> production
3810+
in terms of existing tokens,
3811+
instead relying on a special re-parse from source
3812+
specifically when you're parsing the '@font-face/unicode-range' descriptor.
3813+
(<a href="https://github.com/w3c/csswg-drafts/issues/8835">8835</a>)
3814+
3815+
* Since the above removed the main need to preserve a token's "representation"
3816+
(the original string it was parsed from),
3817+
removed the rest of the references to "representation"
3818+
in the An+B section
3819+
and instead just recorded the few bits of information necessary for that
3820+
(whether or not the number had an explicit sign).
3821+
3822+
* Explicitly noted that some uses
3823+
([=custom properties=], the ''@font-face/unicode-range'' descriptor)
3824+
require access to the original string of a declaration's entire value,
3825+
and marked where that occurs in the parser.
3826+
37833827
<h3 id="changes-CR-20190716">
37843828
Changes from the 16 August 2019 Candidate Recommendation</h3>
37853829

0 commit comments

Comments
 (0)