mirror of
https://github.com/HeyPuter/firefox.git
synced 2026-11-13 20:14:57 -10:00
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
14 lines
497 B
HTML
14 lines
497 B
HTML
<!DOCTYPE html>
|
|
<html>
|
|
<head>
|
|
<title>Missing semicolon at end of block should not keep declaration from being applied</title>
|
|
<link rel="author" title="Steinar H. Gunderson" href="mailto:[email protected]">
|
|
<link rel="help" href="https://crbug.com/1413840">
|
|
<link rel="match" href="missing-semicolon-ref.html">
|
|
<link rel="stylesheet" href="support/missing-semicolon.css">
|
|
</head>
|
|
<body>
|
|
<div class="c">Test passes if this paragraph is green.</div>
|
|
</body>
|
|
</html>
|