standards-positions
standards-positions copied to clipboard
DisplayMediaStreamConstraints.surfaceSwitching
Request for position on an emerging web specification
(Please delete inapplicable rows.)
- WebKittens who can provide input: @youennf
Information about the spec
- Spec Title: Introduce DisplayMediaStreamConstraints.surfaceSwitching
- Spec URL: https://github.com/w3c/mediacapture-screen-share/pull/225/ (merged)
- GitHub repository:
- Issue Tracker (if not the repository's issue tracker):
- Explainer (if not README.md in the repository): https://docs.google.com/document/d/1kqdLoUcwWe8znVCMXyz2FHk9WMylHbIo7gUjhyHmY_w/edit?usp=sharing
Design reviews and vendor positions
- TAG Design Review:
- Mozilla standards-positions issue:
Bugs tracking this feature
- WebKit Bugzilla:
- Radar:
Anything else we need to know
On WebKit dev, @eladalon1983 wrote:
This is a request for WebKit's position on extending getDisplayMedia to also accept DisplayMediaStreamConstraints.surfaceSwitching. The PR that introduced this behavior to the getDisplayMedia spec was approved by Apple engineer Youenn Fablet.
Links:
- ChromeStatus entry: https://chromestatus.com/feature/5067650299330560
@jernoble @eric-carlson, thoughts?
This API is exposing a preference so that UAs can finetune their own UI, if they want to. The fact a UA implements it or not should not cause web compatibilities. In that sense, this is not too controversial.
This preference seems mostly targeted to a particular User Agent (Chrome) UI and I do not think it is something we can leverage in existing macOS UI. I do not anticipate WebKit implementing it, at least in a foreseeing future.
This preference seems mostly targeted to a particular User Agent (Chrome) UI and I do not think it is something we can leverage in existing macOS UI.
Hasn't Apple only recently shipped the feature of letting users switch which screen or window they share?
Hasn't Apple only recently shipped the feature of letting users switch which screen or window they share?
Right, there is OS level UI to enable users to dynamically switch. The point is about the appetite to allow web pages to disable this OS level UI.
I would tend to go with position: neutral
on this one since this is a UA hint.
Barring objections, we'll mark this position: neutral
in a week.
This API is exposing a preference so that UAs can finetune their own UI, if they want to. The fact a UA implements it or not should not cause web compatibilities. In that sense, this is not too controversial.
This preference seems mostly targeted to a particular User Agent (Chrome) UI and I do not think it is something we can leverage in existing macOS UI. I do not anticipate WebKit implementing it, at least in a foreseeing future.
Would it be valuable to implement at least to the level of silently ignore it?