Closed Bug 1791182 Opened 2 years ago Closed 2 years ago

[wpt-sync] Sync PR 35935 - Prevent loading race in SVG <image> intrinsic size test

Categories

(Core :: SVG, task, P4)

Product:
Core
Component:
SVG
Type:
task

Tracking

()

Status:
RESOLVED FIXED
Milestone:
107 Branch
Tracking Flags:
Tracking Status
firefox107 --- fixed

People

(Reporter: mozilla.org, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync downstream])

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

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

Fredrik Söderquist <fs@opera.com> wrote:

Prevent loading race in SVG <image> intrinsic size test

In

external/wpt/svg/geometry/svg-image-intrinsic-size-with-cssstyle-auto.html

an image could have finished loading before we attached the 'load'
handler to it, which would've cause the test to time out.

Wait for the window 'load' event instead (for all the images) to close
this race window.

Minor touch ups (var->const, \< -> <, indentation, trailing comma)
were applied as well.

Bug: 1364327
Change-Id: Ie1eb46d6d8bdb7b24d66293908555b3f7db417d1
Reviewed-on: https://chromium-review.googlesource.com/3900016
WPT-Export-Revision: e1d6bbef2ebfd52afe4b491f9e39006a4ca9a1a3

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

CI Results

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

Total 1 tests and 32 subtests

Status Summary

Firefox

OK : 1
PASS: 32

Chrome

OK : 1
PASS: 32

Safari

OK : 1
PASS: 28
FAIL: 4

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/a3bb3dac2b30
[wpt PR 35935] - Prevent loading race in SVG <image> intrinsic size test, a=testonly

https://hg.mozilla.org/mozilla-central/rev/a3bb3dac2b30

Status: NEW → RESOLVED
Closed: 2 years ago
status-firefox107: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 107 Branch
You need to log in before you can comment on or make changes to this bug.