api.MediaTrackConstraints.displaySurface - in getDisplayMedia no longer supported on safari
Nobody has claimed this yet.
- Dominant language
- JSON
- Stars
- 5.8k
- Forks
- 2.6k
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 186
Description
MDN URL
https://developer.mozilla.org/en-US/docs/Web/API/MediaTrackConstraints/displaySurface
What specific section or headline is this issue about?
Browser compatibility
What information was incorrect, unhelpful, or incomplete?
It says Safari has full support, but it no longer has any effect when provided to getDisplayMedia, possibly since safari changed to use the system picker.
What did you expect to see?
Not supported on safari, or limited support, if this document also refers the setting you get from the track (and if that works, I haven't checked)
Do you have any supporting links, references, or citations?
No response
Do you have anything more you want to share?
No response
MDN metadata
Page report details
- Folder:
en-us/web/api/mediatrackconstraints/displaysurface - MDN URL: https://developer.mozilla.org/en-US/docs/Web/API/MediaTrackConstraints/displaySurface
- GitHub URL: https://github.com/mdn/content/blob/main/files/en-us/web/api/mediatrackconstraints/displaysurface/index.md
- Last commit: https://github.com/mdn/content/commit/cfb7587e3e3122630ad6cbd94d834ecadbe0a746
- Document last modified: 2024-07-26T03:44:38.000Z
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked MDN page and its browser compatibility data for MediaTrackConstraints.displaySurface. Verify Safari behavior for getDisplayMedia and determine whether the reported limitation applies only to the constraint or also to the track setting. Update the relevant compatibility data and run the repository’s validation checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- json
- Domain
- documentation, web-dev
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 70/100