mdn / mdn/browser-compat-data

api.MediaStreamTrack.applyConstraints.cursor_constraint - Missing compatibility data

Open
#27,993 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

blocked browser:chrome data:api
Dominant language
JSON
Stars
5.8k
Forks
2.6k
Avg merge
1d 21h
Merged PRs (30d)
186

Description

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

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the MDN page for MediaTrackSettings.cursor and the reported query api.MediaStreamTrack.applyConstraints.cursor_constraint. Compare the documented browser support with the repository's compatibility data for Chromium, Chrome, Edge, Opera, and Samsung Internet. Done means the cursor support data is present and matches the verified browser history.

Written by the indexing model from the issue text.

Assessment

Domain
content, web-dev
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.