- From: Marcos Cáceres via GitHub <sysbot+gh@w3.org>
- Date: Wed, 18 Aug 2021 01:21:59 +0000
- To: public-device-apis-log@w3.org
@David-Chadwick, reading over the spec text, and giving this some more thought: > you should specify the conditions when MUST does not apply. Then I will be happy as you are giving guidance to implementors when they can legitimately not show this to the user. Having worked with a lot of browser security UX teams, I think this would be overstepping. Browser security XU teams are in the best position to decide when and how indicators are shown. The spec says: > It is RECOMMENDED that a user agent show some form of unobtrusive notification that informs the user when a wake lock is active... I don't think we can mandate anything beyond the above, as browser UX is outside our purview. As an example, browsers like Safari already show notifications (not specifically indicators) when a tab is using significant memory (which could be adapted to show the same thing when a tab is having a significant impact on battery life).  Similarly, Firefox allows users to access a tab's "energy impact" usage via "about:performance":  Thus, to concur with what my colleague @reillyeon said above https://github.com/w3c/screen-wake-lock/issues/282#issuecomment-692937084 - it wouldn't be appropriate for us to mandate anything beyond the above RECOMMENDATION. I'm going to go ahead and close this and there is no further action can be taken here. However, happy to continue to discuss alternative viewpoints. -- GitHub Notification of comment by marcoscaceres Please view or discuss this issue at https://github.com/w3c/screen-wake-lock/issues/282#issuecomment-900741286 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 18 August 2021 01:22:01 UTC