api.Performance.measureUserAgentSpecificMemory - Is listed as experimental
Nobody has claimed this yet.
- Dominant language
- JSON
- Stars
- 5.8k
- Forks
- 2.6k
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 186
Description
What type of issue is this?
Other
What information was incorrect, unhelpful, or incomplete?
measureUserAgentSpecificMemory is listed as "Experimental" which can probably be removed since it hasn't had major changes in two or more years.
We've seen cases of developers being unsure if this is better to use than performance.memory because the "experimental" part can be mildly scary.
What browsers does this problem apply to, if applicable?
No response
What did you expect to see?
Not experimental
Did you test this? If so, how?
N/A
Can you link to any release notes, bugs, pull requests, or MDN pages related to this?
No response
Do you have anything more you want to share?
No response
MDN URL
https://developer.mozilla.org/en-US/docs/Web/API/Performance/measureUserAgentSpecificMemory
MDN metadata
No response
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 at the linked MDN page and locate its browser compatibility data entry. Verify the linked experimental-status guideline against the reported support history, then update the entry so the experimental designation matches the decision and confirm the page no longer shows it as experimental.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- json, web-dev
- Domain
- api, documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100