Files
Steinar H. Gunderson 582da72044 Bug 1815695 [wpt PR 38417] - Fix AtEnd() in fallback eager declaration block parsing., a=testonly
Automatic update from web-platform-tests
Fix AtEnd() in fallback eager declaration block parsing.

When trying to parse a CSS declaration block lazily, and falling back
to eager parsing because we see a { in it, we would not actually end
parsing it properly; the } would not trigger AtEnd(). Beside performance
issues, this would cause the fallback behavior at missing semicolon
at the end of the block to become different. Fix by reading the {
when opening the parse, setting up the block stack properly.

Fixed: 1413840
Change-Id: Ibc165990f75f0ccf1f20415b3add07ca6cd5203b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4232538
Auto-Submit: Steinar H Gunderson <[email protected]>
Commit-Queue: Anders Hartvoll Ruud <[email protected]>
Commit-Queue: Steinar H Gunderson <[email protected]>
Reviewed-by: Anders Hartvoll Ruud <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1102711}

--

wpt-commits: beb84b5061c57a2475938454905409b76b10fac6
wpt-pr: 38417
2023-02-20 09:49:25 +00:00

6 lines
109 B
CSS

.c {
/* This { needs to be there to send Chromium into a different path. */
color: red;
color: green
}