- From: Mounir Lamouri via GitHub <sysbot+gh@w3.org>
- Date: Mon, 19 Nov 2018 19:24:44 +0000
- To: public-device-apis-log@w3.org
I think we should differentiate these three things: - is the use case valid for the Web? - should we design an API resolving this specific use case or resolving this use case among other things? - should we hard link this feature to Wake Lock? In my opinion, even though the use case is valid and we should resolve it, it's unclear that it's a good idea going forward to try to resolve this use case specifically. In general, the Web Platform is looking at offering low level APIs as high level APIs end up too limited. I think that we could offer a better API if the app could simply set the brightness from 0 to 1 with pretty much the same threat model. Furthermore, linking the API to Wake Lock creates a similar limitation: even though for scanning use cases (eg. Starbucks), linking the two APIs make sense, as a platform, we need to think beyond this and we shouldn't assume anyone interested to change the brightness wants the screen to stay on. -- GitHub Notification of comment by mounirlamouri Please view or discuss this issue at https://github.com/w3c/wake-lock/issues/129#issuecomment-440011878 using your GitHub account
Received on Monday, 19 November 2018 19:24:45 UTC