Closed Bug 1815522 Opened 3 years ago Closed 3 years ago

[wpt-sync] Sync PR 38393 - [rsafor] Add test for missing origin param

Categories

(Testing :: web-platform-tests, task, P4)

task

Tracking

(firefox112 fixed)

RESOLVED FIXED
112 Branch
Tracking Status
firefox112 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

Matt Reichhoff <mreichhoff@chromium.org> wrote:

[rsafor] Add test for missing origin param

The parameter is required, so a rejection is expected.

Bug: 1410556
Change-Id: I6106e1ab49034539d51437b74b11853c2fe3b0e5
Reviewed-on: https://chromium-review.googlesource.com/4228312
WPT-Export-Revision: 1c6e7a57b1cb2aef28d8b1c09e0e068f57c75d6f

CI Results

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

Total 1 tests and 11 subtests

Status Summary

Firefox

OK : 1
FAIL: 11

Chrome

OK : 1
FAIL: 11

Safari

OK : 1
FAIL: 11

Links

GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

  • /top-level-storage-access-api/tentative/requestStorageAccessForOrigin.sub.https.window.html [wpt.fyi]
    • [top-level-context] document.requestStorageAccessForOrigin() should be supported on the document interface: FAIL (Chrome: FAIL, Safari: FAIL)
    • [top-level-context] document.requestStorageAccessForOrigin() should be rejected when called with no argument: FAIL (Chrome: FAIL, Safari: FAIL)
    • [top-level-context] document.requestStorageAccessForOrigin() should be rejected by default with no user gesture: FAIL (Chrome: FAIL, Safari: FAIL)
    • [non-fully-active] document.requestStorageAccessForOrigin() should not resolve when run in a detached frame: FAIL (Chrome: FAIL, Safari: FAIL)
    • [non-fully-active] document.requestStorageAccessForOrigin() should not resolve when run in a detached DOMParser document: FAIL (Chrome: FAIL, Safari: FAIL)
    • [top-level-context] document.requestStorageAccessForOrigin() should be resolved when called properly with a user gesture and the same site: FAIL (Chrome: FAIL, Safari: FAIL)
    • [top-level-context] document.requestStorageAccessForOrigin() should be rejected when called with an invalid site: FAIL (Chrome: FAIL, Safari: FAIL)
    • [top-level-context] document.requestStorageAccessForOrigin() should be rejected when called with an opaque origin: FAIL (Chrome: FAIL, Safari: FAIL)
    • [same-origin-frame] document.requestStorageAccessForOrigin() should be supported on the document interface: FAIL (Chrome: FAIL, Safari: FAIL)
    • [same-origin-frame] document.requestStorageAccessForOrigin() should be rejected when called with no argument: FAIL (Chrome: FAIL, Safari: FAIL)
    • [same-origin-frame] document.requestStorageAccessForOrigin() should be rejected when called in an iframe: FAIL (Chrome: FAIL, Safari: FAIL)
Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/ca391bcb9e37 [wpt PR 38393] - [rsafor] Add test for missing origin param, a=testonly https://hg.mozilla.org/integration/autoland/rev/460a43486d76 [wpt PR 38393] - Update wpt metadata, 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.