- From: Marcos Cáceres via GitHub <sysbot+gh@w3.org>
- Date: Sun, 25 Nov 2018 04:16:01 +0000
- To: public-device-apis-log@w3.org
@mounirlamouri wrote: > Designed an API only based on use cases and not trying to expand from them seems dangerous and may end up with design flaws. Offering a larger ability will trigger new use cases we did not think of. I'm sympathetic to this argument - but the potential to abuse and user annoyance as we described above is too obvious and great. Fine grained control is definitely not something we would consider implementing in Firefox. > I wouldn't worry much about applications trying to change the brightness as they wouldn't have an effect unless they are visible and the UA could put min values to make sure they don't attempt to keep the screen black. I worry :( I don't think I can sell this internally. @HenrikJoreteg wrote: > In my opinion, the best APIs are where you clearly and succinctly express intent. So perhaps rather than arbitrarily saying "full brightness" what if it was something along the lines of "optimizeForScanning"? Or even "optimizeForContrast" I guess we could go down this route, but we've only come up with the a single purpose. We could make a working assumption that "optimizeForContrast" is the default, and then enhance the API if we come up with other things (based on actual apps needing to do actual things - like StarBucks). -- GitHub Notification of comment by marcoscaceres Please view or discuss this issue at https://github.com/w3c/wake-lock/issues/129#issuecomment-441414094 using your GitHub account
Received on Sunday, 25 November 2018 04:16:04 UTC