Closed Bug 1893435 Opened 6 months ago Closed 1 month ago

[wpt-sync] Sync PR 45909 - Fix meta refresh test

Categories

(Core :: DOM: Core & HTML, task, P4)

task

Tracking

()

RESOLVED FIXED
132 Branch
Tracking Status
firefox132 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

Psychpsyo <psychpsyo@gmail.com> wrote:

Fix meta refresh test

Turns out that it didn't need a long timeout, but just had to wait for
the iframe to load completely, which is when, as per the spec, the
refresh timer should start.
(Single, tiny HTML file in this case, really shouldn't take long but I
guess the browser is pretty busy when all the tests are run at once?)
I can only go off of my local test results for this currently
but I hope that this fixes the failures that came up.

Bug: 333976551
Change-Id: I134348aac4f97b321875b37a7c179432585bd3fc
Reviewed-on: https://chromium-review.googlesource.com/5488199
WPT-Export-Revision: 808512d9bc23b3bd1f245826e927892ce8175a29

Component: web-platform-tests → DOM: Core & HTML
Product: Testing → Core
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Whiteboard: [wptsync downstream error] → [wptsync downstream]

CI Results

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

Total 1 tests and 3 subtests

Status Summary

Firefox

OK : 1
PASS : 3

Chrome

OK : 1
PASS : 3

Safari

PASS : 1
TIMEOUT: 2
NOTRUN : 1

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/bf9ca1980a69 [wpt PR 45909] - Fix meta refresh test, a=testonly https://hg.mozilla.org/integration/autoland/rev/7d017635c02c [wpt PR 45909] - Update wpt metadata, a=testonly
Status: NEW → RESOLVED
Closed: 1 month ago
Resolution: --- → FIXED
Target Milestone: --- → 132 Branch
You need to log in before you can comment on or make changes to this bug.