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

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

That's a reasonable request, and as I mentioned previously, this is now required by MacOS.   The Presentation API allows browsers to request additional permission before discovering devices, or to not implement background discovery at all so that it happens only when starting a presentation.  So I don't think there's any incompatibility with your wishes here.

> In summary, all of this behavior seems very inconsistent from both the User and the Programmers point of view.

I generally agree with your point that there are some overlaps in functionality between Presentation API and Window Management API.  Rather than try to coerce the APIs to function identically, I think they serve different use cases.  Window Management is closer to what you want, as far as I can tell - automating the placement of content on a fixed set of displays.  The Window Management API [permits use of wireless displays as well](https://www.w3.org/TR/window-management/#usage-overview-screen-extended).  

What types of displays and display connections are you using for your hobby project?  HDMI, Chromecast, something else?


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


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

Received on Friday, 28 March 2025 17:27:11 UTC