[wpt-sync] Sync PR 36740 - Remove reliance on "global" mutable state.
Categories
(Testing :: web-platform-tests, task, P4)
Tracking
(firefox108 fixed)
| Tracking | Status | |
|---|---|---|
| firefox108 | --- | fixed |
People
(Reporter: wpt-sync, Unassigned)
References
()
Details
(Whiteboard: [wptsync downstream])
Sync web-platform-tests PR 36740 into mozilla-central (this bug is closed when the sync is complete).
PR: https://github.com/web-platform-tests/wpt/pull/36740
Details from upstream follow.
Chris Fredrickson <cfredric@chromium.org> wrote:
Remove reliance on "global" mutable state.
This helper attempted to use g_clickID to give each button a unique
ID, but didn't account for the fact that different instances of the
script have their own variables, so that variable isn't truly global,
and therefore IDs can be reused across iframes. This CL avoids this
issue by making the caller provide the ID explicitly, so it's at least
more obvious if two invocations of the helper reuse the same ID.(I found this issue while debugging crbug.com/1379595, and while this
wasn't the cause of that bug, I still think it's worth fixing.)Bug: 1379595
Change-Id: Ie208bae11d5eb87d9bbc9bb11aff68ce540d71a7Reviewed-on: https://chromium-review.googlesource.com/3993924
WPT-Export-Revision: 6805006336dedff983c518097b0f0ad9cc06d37e
| Assignee | ||
Comment 1•3 years ago
|
||
| Assignee | ||
Comment 2•3 years ago
|
||
| Assignee | ||
Comment 3•3 years ago
|
||
CI Results
Ran 0 Firefox configurations based on mozilla-central, and Firefox, Chrome, and Safari on GitHub CI
Total 3 tests and 5 subtests
Status Summary
Firefox
OK : 2
PASS : 27
FAIL : 3
TIMEOUT: 2
NOTRUN : 2
Chrome
OK : 2
PASS : 2
FAIL : 18
ERROR : 1
Safari
OK : 3
PASS : 20
FAIL : 13
Links
Details
New Tests That Don't Pass
- /storage-access-api/requestStorageAccess.sub.window.html [wpt.fyi]:
TIMEOUT(Chrome:ERROR, Safari:OK)- [non-fully-active] document.requestStorageAccess() should not resolve when run in a detached frame:
TIMEOUT(Safari:FAIL) - [non-fully-active] document.requestStorageAccess() should not resolve when run in a detached DOMParser document:
NOTRUN(Safari:FAIL) - [top-level-context] document.requestStorageAccess() should be resolved when called properly with a user gesture:
NOTRUN(Safari:FAIL)
- [non-fully-active] document.requestStorageAccess() should not resolve when run in a detached frame:
- /storage-access-api/storageAccess.testdriver.sub.html [wpt.fyi]
- Set up storage access rules:
FAIL(Chrome:FAIL, Safari:FAIL) - [third-party-blocked-on-first-party-site] Cookie access is allowed: false:
FAIL(Chrome:FAIL, Safari:FAIL) - [third-party-blocked-all] Cookie access is allowed: false:
FAIL(Chrome:FAIL, Safari:FAIL)
- Set up storage access rules:
Comment 5•3 years ago
|
||
| bugherder | ||
Description
•