mdn
api.MediaStreamTrack.applyConstraints.cursor_constraint - Missing compatibility data
What type of issue is this?
Incorrect support data (example: BrowserX says "86" but support was added in "40")
What information was incorrect, unhelpful, or incomplete?
Hi! This data is missing. From looking around it seems it might just not exist in browsers / Chrome anymore?
What browsers does this problem apply to, if applicable?
Chromium (Chrome, Edge 79+, Opera, Samsung Internet)
What did you expect to see?
Cursor browser data.
Did you test this? If so, how?
Looking at https://developer.mozilla.org/en-US/docs/Web/API/MediaTrackSettings/cursor
Can you link to any release notes, bugs, pull requests, or MDN pages related to this?
https://developer.mozilla.org/en-US/docs/Web/API/MediaTrackSettings/cursor
Do you have anything more you want to share?
No response
MDN URL
https://developer.mozilla.org/en-US/docs/Web/API/MediaTrackSettings/cursor
MDN metadata
MDN page report details
- Query:
api.MediaStreamTrack.applyConstraints.cursor_constraint - Report started: 2025-09-25T04:50:34.233Z
We would record this data as api.MediaStreamTrack.cursor_constraint.
It looks like the MediaTrackSettings.cursor property was implemented in Chrome 71 together with displaySurface and logicalSurface:
https://github.com/chromium/chromium/commit/24e31432c12caf3d26cc9d87c9c6461d6682d509#diff-7f9bb5ec65982897a84b32096a7d89aa6e4a4f85484fe4b140cdc7484f815a07R56
However, it is not obvious if these are really supported without a flag, and since when: According to BCD, displaySurface was added in Chrome 107, and logicalSurface was never added in Chrome.
To update this data, we need some test case.
@hamishwillee Do you have thoughts or ideas?
