Closed Bug 1727806 Opened 3 years ago Closed 3 years ago

[wpt-sync] Sync PR 30201 - Cache SVGResource cycle status less aggressively

Categories

(Core :: SVG, task, P4)

task

Tracking

()

RESOLVED FIXED
93 Branch
Tracking Status
firefox93 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

b'Fredrik S\xc3\xb6derqvist <fs@opera.com>' wrote:

Cache SVGResource cycle status less aggressively

Only consider negative cycle status, and always recheck otherwise. This
is less optimistic, but is required by the way we invalidate (or, don't)
cycle status when client associations change. It also matches our
behavior prior to 27490b820dae84e0c7f623806a6691c2a742ced7 (where we
only avoided re-checking known cycles).

Bug: 1240015
Change-Id: If616922c843156157fe717cd94aa586bd5526b33

Reviewed-on: https://chromium-review.googlesource.com/3122150
WPT-Export-Revision: d49fd8b3b4dc590bb3fb8c553b180802bfbf633c

Component: web-platform-tests → SVG
Product: Testing → Core

CI Results

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

Total 1 tests

Status Summary

Firefox

PASS : 1

Chrome

CRASH: 1

Safari

PASS : 1

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/712f06c26edf [wpt PR 30201] - Cache SVGResource cycle status less aggressively, a=testonly
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → 93 Branch
You need to log in before you can comment on or make changes to this bug.