#543: Screen Wake Lock API

Visit on Github.

Opened Aug 6, 2020

Saluton TAG!

I'm requesting a TAG review of Screen Wake Lock API.

This document specifies an API that allows web applications to request a screen wake lock. Under the right conditions, and if allowed, the screen wake lock prevents the system from turning off a device's screen.

Further details:

  • I have reviewed the TAG's API Design Principles
  • The group where the work on this specification is currently being done: W3C DAS WG
  • Major unresolved issues with or opposition to this specification:
  • This work is being funded by:

You should also know that...

Changes since the last CR: https://w3c.github.io/screen-wake-lock/#changes-20171214

We'd prefer the TAG provide feedback as (please delete all but the desired option):

☂️ open a single issue in our GitHub repo for the entire review

Discussions

Comment by @alice Sep 15, 2020 (See Github)

Could you comment as to why there is no explainer for this API?

Comment by @kenchris Sep 15, 2020 (See Github)

https://github.com/w3c/screen-wake-lock/issues/284

Comment by @rakuco Sep 21, 2020 (See Github)

Hi, everyone. FYI, the PR above was merged earlier today and we now have an explainer in the repository.

Comment by @alice Sep 22, 2020 (See Github)

Thank you! I added it to the top comment as well.

Comment by @alice Sep 23, 2020 (See Github)

That explainer does what the name implies, thanks so much for your effort there.

@cynthia and I are both happy with this.

My only feedback would be that it would be nice to see a note explaining why you need to pass "screen" to WakeLock.request() when it's the only possible value - my guess would be that there is an intent to re-use this API for the future System Wake Lock API, but it would be good to be clear on that. Also, a link out to discussion of that API might also be useful context.

Comment by @rakuco Sep 23, 2020 (See Github)

My only feedback would be that it would be nice to see a note explaining why you need to pass "screen" to WakeLock.request() when it's the only possible value - my guess would be that there is an intent to re-use this API for the future System Wake Lock API, but it would be good to be clear on that. Also, a link out to discussion of that API might also be useful context.

Thanks, I've sent w3c/screen-wake-lock#288 to tackle this one.

Comment by @cynthia Jan 13, 2021 (See Github)

We noticed that the issue has been resolved on your end. Thanks! We're happy to see this move forward.