Re: [mediacapture-image] Determine how PTZ permission prompts are supposed to work (#243)

> maybe instead of saying "any algorithm", we could link to a specific section about gUM.

Yes, I would think it helps.

> there's an [example in the spec](https://w3c.github.io/mediacapture-image/#example1)

I am not clear on whether it is possible for a browser to allow a user to say: yes for camera but no for PTZ in case of getUserMedia({ video : { pan : true })?
If it is possible, is it mandatory for a user agent to support that or is it UX territory?
If it is possible, how is the web page notified of the user decision (getCapabilities, navigator.permissions.query).
If it is possible, browser A supports it but browser B does not, web pages might be coded so that getUserMedia promise fulfilment means PTZ is granted for instance while this might not be true on all browsers, hence compat issues.
If it is possible, we enter in UX that might ask variable questions like : camera-only, microphone-only, camera+microphone, cameraPTZ-only, cameraPTZ+microphone... This adds a lot of variability to the question asked to the user.

Another related question (maybe this is already clear in the spec). If PTZ is supported by the camera and page has a MediaStreamTrack, what would return capabilities.pan and applyConstraints({pan: xxx}) in the following cases:
- page did not ask for { pan : true } in getUserMedia
- page asked for { pan : true } but user decided to only grant camera, not PTZ.

The primer also says: "It will also be possible for users to revoke the PTZ permission by itself, while keeping the camera permission". Is there anything the spec should say about this case? For instance, in terms of what happens to live cameraPTZ track(s)? media capture main indicates (not very strongly though) that the live tracks get ended if permission is revoked.

-- 
GitHub Notification of comment by youennf
Please view or discuss this issue at https://github.com/w3c/mediacapture-image/issues/243#issuecomment-673977708 using your GitHub account


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

Received on Friday, 14 August 2020 09:14:24 UTC