W3C home > Mailing lists > Public > public-device-apis-log@w3.org > October 2019

Re: [wake-lock] Anyone implementing "system" lock? (#232)

From: Marcos Cáceres via GitHub <sysbot+gh@w3.org>
Date: Tue, 08 Oct 2019 11:01:23 +0000
To: public-device-apis-log@w3.org
Message-ID: <issue_comment.created-539462299-1570532482-sysbot+gh@w3.org>
> Yes just like Android, certain things already implicitly run a wake lock, but those are special cases, like background downloads, and media play back.

I guess I'm trying to tease out compelling use cases and if I can make a case within Mozilla to support these.

> If I am processing an image (say resize before upload etc) that won't be handled, or geolocation cases and the likes.

Let's put the geo one aside, as geo in workers is not a thing AFAIK. The image/data processing in a worker case might be interesting tho. Have we explored having dedicated workers be granted a longer lifetime based on type?... Given that "system" locks can only be used in a Worker, and wakes locks are completely unreliable (can be released for whatever reason), I wonder if we should just have "system lock-like behavior" be a request when the worker is created. 

That could hint the the UA that "this worker is long lived" and to treat it specially with a system lock for as long as possible. Just a random thought.  

GitHub Notification of comment by marcoscaceres
Please view or discuss this issue at https://github.com/w3c/wake-lock/issues/232#issuecomment-539462299 using your GitHub account
Received on Tuesday, 8 October 2019 11:01:28 UTC

This archive was generated by hypermail 2.4.0 : Monday, 4 July 2022 12:47:57 UTC