- From: Anssi Kostiainen via GitHub <sysbot+gh@w3.org>
- Date: Mon, 08 Apr 2019 11:23:04 +0000
- To: public-device-apis-log@w3.org
I'm generally in favor of not changing names exposed through bindings unless we have evidence the current names cause confusion, and there's a better alternative that would significantly improve the situation. Any names we choose, will be misunderstood by some. What we can do in the context of this issue first without renaming `WakeLockType` enum values is to make sure the descriptions of these terms are as accurate and complete reflections of reality as possible: >A **screen wake lock** prevents the screen from turning off. Only visible documents can acquire the wake lock. >A **system wake lock** prevents the CPU from entering a deep power state. This may also prevent communication chips such as celular or Wi-Fi from sleeping. If the clarified descriptions are in conflict with the enum values, that makes for a stronger case to renamed the values too. -- GitHub Notification of comment by anssiko Please view or discuss this issue at https://github.com/w3c/wake-lock/issues/177#issuecomment-480791728 using your GitHub account
Received on Monday, 8 April 2019 11:23:06 UTC