css.selectors.-webkit-meter-bar - Seems to be incorrectly marked as "deprecated"
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?
Incorrect support data (example: BrowserX says "86" but support was added in "40")
What information was incorrect, unhelpful, or incomplete?
The information seems to be incorrect; the ::-webkit-meter-bar pseudo-element still seems to be fully supported, with no plans to deprecate.
What browsers does this problem apply to, if applicable?
Chromium (Chrome, Edge 79+, Opera, Samsung Browser)
What did you expect to see?
I expected the ::-webkit-meter-bar pseudo-element to be marked as non-standard, but not deprecated.
Did you test this? If so, how?
I've used this pseudo-element in live projects with modern, up-to-date versions of Chrome and Edge, and it works properly, without any error messages appearing in the console.
Can you link to any release notes, bugs, pull requests, or MDN pages related to this?
It seems that it was marked as deprecated in commit 11fb2b3 of PR #23939 to complete issue #23840. However, it appears that the error message mentioned by that issue was a mistake and was incorrectly being thrown for valid pseudo-elements, including ::-webkit-meter-bar.
See this comment about removing the error message, as well as this commit that removes the error message and provides more info in the commit message.
Do you have anything more you want to share?
No response
MDN URL
No response
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 by locating the css.selectors.-webkit-meter-bar entry in the compatibility data and review the linked Chromium commit and CSSWG discussion. Verify the current browser behavior and update the entry so it reflects the supported, non-standard status without the deprecated flag. Run the repository's data validation checks to confirm the change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css
- Domain
- data, web-dev
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 76/100