| commit | f0fa52c0bf28efe51efe8ac4499668040357db76 | |
| author | Joey Arhar <jarhar@chromium.org> | |
| Tue, 2 Aug 2022 10:32:07 +0000 (2 10:32 +0000) | ||
| committer | moz-wptsync-bot <wptsync@mozilla.com> | |
| Wed, 3 Aug 2022 10:10:02 +0000 (3 10:10 +0000) | ||
| tree | bae38acca40833cee14683076b5bc2dd7e2a73e1 | treesnapshot (tar.gz zip) |
| parent | 08f76e786ddd36884d66b2866cc3bd599f6ea159 | commitdiff |
Bug 1781442 [wpt PR 34744] - Don't re-lock DisplayLocks during forced unlock, a=testonly
Automatic update from web-platform-tests
Don't re-lock DisplayLocks during forced unlock
When a DisplayLock is unlocked via ForceUnlockIfNeeded, subsequent
updates to the DisplayLock can cause it to become locked again which is
problematic.
This patch prevents the DisplayLock from being locked again until the
next frame.
Fixed: 1338135
Change-Id: I07790658e25ea9fe2f4e8de154e3a58e7e08892b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3751710
Commit-Queue: Joey Arhar <jarhar@chromium.org>
Reviewed-by: Vladimir Levin <vmpstr@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1028405}
--
wpt-commits: 0966be69c8686977b6e0c1efc6f9f020055aa474
wpt-pr: 34744
Automatic update from web-platform-tests
Don't re-lock DisplayLocks during forced unlock
When a DisplayLock is unlocked via ForceUnlockIfNeeded, subsequent
updates to the DisplayLock can cause it to become locked again which is
problematic.
This patch prevents the DisplayLock from being locked again until the
next frame.
Fixed: 1338135
Change-Id: I07790658e25ea9fe2f4e8de154e3a58e7e08892b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3751710
Commit-Queue: Joey Arhar <jarhar@chromium.org>
Reviewed-by: Vladimir Levin <vmpstr@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1028405}
--
wpt-commits: 0966be69c8686977b6e0c1efc6f9f020055aa474
wpt-pr: 34744
| testing/web-platform/tests/fullscreen/crashtests/content-visibility-crash.html | [new file with mode: 0644] | blob |