- From: Mark Foltz via GitHub <sysbot+gh@w3.org>
- Date: Sat, 22 Mar 2025 19:27:29 +0000
- To: public-secondscreen@w3.org
The situation is slightly different for Bluetooth and USB. In those cases, the set of eligible targets is relatively fixed from the host device's point of view, either through previous Bluetooth pairing, or physical connection through USB. Therefore, if the user has previously granted a site access to a device, it's likely that the device will be available in the future. Presentation API targets are typically discovered through network multicast, which results in an ephemeral list of devices depending on which network sender and receiver devices happen to be connected to (if at all). If the browser finds a device that the site has not connected to before, it won't be in the enumeration, so every site will need to implement a fallback on having a browser-mediated dialog to allow the user to select non-enumerated devices. Also, the user should provide consent before presentation starts, because the site will be placing information on a shared display. So even if the site has a device enumeration and a way to request presentation on a device, there should be confirmation by a trusted browser dialog. In summary, for the general presentation scenario, site enumeration and direct selection of presentation receivers creates more problems than it solves from privacy and user interface complexity points of view. There might be some use cases where site driven selection makes sense, such as a kiosk or other configuration with a fixed set of displays. In those scenarios, the browser could be customized with policies to select displays on behalf of the user. Also, the Window Management API is set up to better support these scenarios since it allows display enumeration and direct placement of content on attached displays (once permission is granted). Happy to discuss further, but maybe a concrete use case would help focus the discussion more. -- GitHub Notification of comment by markafoltz Please view or discuss this issue at https://github.com/w3c/presentation-api/issues/526#issuecomment-2745420264 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 22 March 2025 19:27:30 UTC