Closed Bug 1481568 Opened 7 years ago Closed 7 years ago

[wpt-sync] Sync PR 12343 - [html] Verify synchronicity of beforeunload event

Categories

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

Product:
Core
Component:
DOM: Core & HTML
Type:
enhancement

Tracking

()

Status:
RESOLVED FIXED
Milestone:
mozilla63
Tracking Flags:
Tracking Status
firefox63 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync downstream])

Sync web-platform-tests PR 12343 into mozilla-central (this bug is closed when the sync is complete). PR: https://github.com/web-platform-tests/wpt/pull/12343 Details from upstream follow. Mike Pennisi <mike@mikepennisi.com> wrote: > [html] Verify synchronicity of beforeunload event > > After reviewing all the files that reference "beforeunload" (as reported by `git grep -l beforeunload`), I can't find coverage for this behavior. There are a number of ways to observe this behavior. The choice of `location.href` is arbitrary, and I'm open to suggestion on using some other API either in place of `location.href` or in addition to it. > > Browser | Result > ------------|------- > Chrome 68 | :x: > Edge 17 | :x: > Firefox 61 | :heavy_check_mark: > IE 11 | :heavy_check_mark: > Safari 11.1 | :x: > > This came up in the context of gh-12290, where I authored a test to support asynchronous behavior. A number of tests in WPT are written in this way, but they generally concern other details of the specification, so I suppose it's acceptable for them to be loose in this regard. > >
Component: web-platform-tests → DOM
Product: Testing → Core
Ran 1 tests and 1 subtests OK : 1 PASS : 1
Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/9ee4484da82c [wpt PR 12343] - [html] Verify synchronicity of beforeunload event, a=testonly
https://hg.mozilla.org/mozilla-central/rev/9ee4484da82c
Status: NEW → RESOLVED
Closed: 7 years ago
status-firefox63: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla63
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.