W3C home > Mailing lists > Public > public-device-apis-log@w3.org > December 2018

Re: [wake-lock] What do the wakelocks actually do? (#138)

From: Jeffrey Yasskin via GitHub <sysbot+gh@w3.org>
Date: Wed, 12 Dec 2018 19:32:36 +0000
To: public-device-apis-log@w3.org
Message-ID: <issue_comment.created-446714689-1544643155-sysbot+gh@w3.org>

One browser-level power-saving abstraction is described in https://github.com/WICG/page-lifecycle, edited by @shubhie.

-- 
GitHub Notification of comment by jyasskin
Please view or discuss this issue at https://github.com/w3c/wake-lock/issues/138#issuecomment-446714689 using your GitHub account

Received on Wednesday, 12 December 2018 19:32:38 UTC

This message: [ Message body ]
Next message: Chris Dumez via GitHub: "[deviceorientation] Add API for requesting permission to receive device motion / orientation events (#57)"
Previous message: Jeffrey Yasskin via GitHub: "[wake-lock] What do the wakelocks actually do? (#138)"
In reply to: Jeffrey Yasskin via GitHub: "[wake-lock] What do the wakelocks actually do? (#138)"

Mail actions: [ respond to this message ] [ mail a new topic ]
Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ]
Help: [ How to use the archives ] [ Search in the archives ]

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