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

Marvin-Brouwer has just created a new issue for https://github.com/w3c/presentation-api:

== [Question] Why does the spec require a browser to select the presentation device ==
I've been reading the closed issues and I've skimmed through the spec before posting this.
I don't really understand why I'm not allowed to get a list of objects containing the presentable device's name, id, capability etc. and call `presentationRequest.start('deviceId')` or something similar.
Like the [Media Capture and Streams API](https://developer.mozilla.org/en-US/docs/Web/API/Media_Capture_and_Streams_API).

I've seen someone speculate here https://github.com/w3c/presentation-api/issues/315#issuecomment-225901496 that it might be because you want to give users control over which device they want to select. Preventing a website from just picking one at random and causing strange situations.
However, I haven't seen any official statement as to why this is specced the way it is.
If you make a mobile app you get the option to list out devices and style them inside of the app, so to me it makes sense a web site could do something similar. If I'm wrong that's fine, but I'd like to be able to read why the decision has been made.

Please view or discuss this issue at https://github.com/w3c/presentation-api/issues/526 using your GitHub account


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

Received on Saturday, 28 December 2024 09:59:09 UTC