New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 872530 link

Starred by 1 user
Status: Assigned
Owner:
█ mrunal.k...@intel.com
Last visit > 30 days ago
Cc:
mlamouri@chromium.org
foolip@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug

Blocking:
issue 257511



Sign in to add a comment

Wake Lock API tests timing out waiting for 'visibilitychange' event

Project Member Reported by mrunal.k...@intel.com, Aug 9 
For some reason, two of the Wake Lock API tests are timing out waiting for 'visibilitychange' event.
external/wpt/wake-lock/wakelock-applicability-manual.https.html [ Timeout ]
external/wpt/wake-lock/wakelock-document-hidden.https.html [ Timeout ]

Comment 1 by mlamouri@chromium.org, Aug 9

Cc: foolip@chromium.org mlamouri@chromium.org
Status: Assigned (was: Untriaged)
Do we have ways to mock visibility changes in WPT? +foolip@

Comment 2 by kereliuk@google.com, Aug 15 

https://github.com/web-platform-tests/wpt/pull/10751 should provide an API to change the visibility (by minimization) when it lands!

Comment 3 by foolip@chromium.org, Aug 15 

I've confirmed that at least in Chrome Canary on Mac, minimizing and restoring the window does fire the visibilitychange event and cycle document.visibilityState through "hidden" and "visible", so that API seems right.

There is some risk that it doesn't actually work in content_shell, which is special in many ways, but we will have to see.
►

Sign in to add a comment