Closed Bug 1815695 Opened 3 years ago Closed 3 years ago

[wpt-sync] Sync PR 38417 - Fix AtEnd() in fallback eager declaration block parsing.

Categories

(Core :: CSS Parsing and Computation, task, P4)

task

Tracking

()

RESOLVED FIXED
112 Branch
Tracking Status
firefox112 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

Sync web-platform-tests PR 38417 into mozilla-central (this bug is closed when the sync is complete).

PR: https://github.com/web-platform-tests/wpt/pull/38417
Details from upstream follow.

Steinar H. Gunderson <sesse@chromium.org> wrote:

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/4232538
WPT-Export-Revision: 33bbfcd889e0795913ef1e3131f8902e6ba6c7b8

Component: web-platform-tests → CSS Parsing and Computation
Product: Testing → Core

CI Results

Ran 0 Firefox configurations based on mozilla-central, and Firefox, Chrome, and Safari on GitHub CI

Total 1 tests

Status Summary

Firefox

PASS: 1

Chrome

FAIL: 1

Safari

PASS: 1

Links

GitHub PR Head
GitHub PR Base

Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/1f429bb785ee [wpt PR 38417] - Fix AtEnd() in fallback eager declaration block parsing., a=testonly
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → 112 Branch
You need to log in before you can comment on or make changes to this bug.