- From: Marcos Cáceres via GitHub <sysbot+gh@w3.org>
- Date: Tue, 29 Sep 2020 00:25:02 +0000
- To: public-device-apis-log@w3.org
I agree with @reillyeon... more generally, I'm looking at, for example, how finding which tab is making noise is handled: ![Screen Shot 2020-09-29 at 10 20 35 am](https://user-images.githubusercontent.com/870154/94498416-6e328f80-023d-11eb-96e8-707ecdf3623c.png) I.e., showing the origin is not as helpful as allowing a user to get to a particular tab that is using a resource (irrespective of origin... or even without showing any origin at all). -- GitHub Notification of comment by marcoscaceres Please view or discuss this issue at https://github.com/w3c/screen-wake-lock/issues/278#issuecomment-700352173 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 29 September 2020 00:25:04 UTC