Re: [presentation-api] [Question] Why does the spec require a browser to select the presentation device (#526)

> 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.

I don't agree, all the "explorable devices" in my network are devices like Chromecasts or smart tv's they are stationary. And USBdevices, like flash drives, will most likely be disconnected after use.
To me this is exactly the opposite of your statement.

> 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.

I completely agree, however, I think this consent should be given prior to the enumerating.  
I would like to decide whether a browser may scan my network at all before it does so.  
Whether the site get's to see this or not.  

> 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).

But, shouldn't these APIs act in a similar way?
It seems odd UX to me that the window API requests me if I'm okay with the site having access and the screen cast API just asking me "where do you want this site to stream to" and suddenly showing me devices on my network.
Additionally, I think it's kind of odd that the screen presentation API also adds the "additional screens" as an option, but not the primary screen. And, there is no way to either opt-out of having windows as share target or adding the main window as one.
In summary, all of this behavior seems very inconsistent from both the User and the Programmers point of view. 

> Happy to discuss further, but maybe a concrete use case would help focus the discussion more.

I don't really have a use-case, I was just playing around with possibly replacing my current chomecast button on a hobby project (which I realize also has these issues).

-- 
GitHub Notification of comment by Marvin-Brouwer
Please view or discuss this issue at https://github.com/w3c/presentation-api/issues/526#issuecomment-2746267869 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Sunday, 23 March 2025 15:18:43 UTC