- From: Thomas Steiner via GitHub <sysbot+gh@w3.org>
- Date: Mon, 19 Sep 2022 09:38:36 +0000
- To: public-device-apis-log@w3.org
Thanks, @beaufortfrancois, this reflects the consensus of the meeting well I think. Some remarks: - On top of auto-boosting when the element becomes visible, we talked about UAs making an affordance like a button available that would trigger the actual brightness boost. This could be offered as an alternative UA behavior. - The two first restrictions (_"The website is in a secure browsing context."_ and _"The element is NOT in a cross-origin iframe."_) might not actually be necessary. - The 1/4 of the screen size requirement could probably be formulated with more leeway for UAs to do what they think is best. One additional idea might be to say that _(i)_, dynamically inserted attributes in the user gesture that triggered a fullscreen request or _(ii)_, statically already existing attributes in the fullscreen'ed element could be always honored, for example, for proprietary codes ([example](https://web.dev/mini-app-about/#discovery:~:text=Scanning%20this%202d%20barcode%20with%20the%20WeChat%20app%20launches%20a%20demo%20mini%20app.)). -- GitHub Notification of comment by tomayac Please view or discuss this issue at https://github.com/w3c/screen-wake-lock/issues/348#issuecomment-1250794373 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 19 September 2022 09:38:38 UTC