mdn / mdn/browser-compat-data

css.selectors.has - Add table of :has() support for each pseudo-class

Open
#17,818 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

browser:multiple data:css needs collector test
Dominant language
JSON
Stars
5.8k
Forks
2.6k
Avg merge
1d 21h
Merged PRs (30d)
186

Description

What type of issue is this?

Missing compatibility data

What information was incorrect, unhelpful, or incomplete?

Currently, MDN BCD has a single row of compat data about :has().

It would be helpful for there to instead be a much larger set of data that enumerates what arguments are supported inside of :has().
For example:

  • :has(:not)
  • :has(:first-of-type)
  • :has(:modal)
  • :has(:playing)
    and there are many, many more.

Some of these are supported in certain browsers. Others are not. Right now there's not a canonical place for developers to look up what is and is not supported.

Pseudo-elements are not supported inside :has(). :has(:has( )) is not allowed. And there are other restrictions according to the standard / see CSSWG resolutions.

What browsers does this problem apply to, if applicable?

No response

What did you expect to see?

No response

Did you test this? If so, how?

No response

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/CSS/:has

MDN metadata

No response

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 from the existing :has() compatibility entry associated with the MDN :has page and review the CSSWG restrictions cited in the issue. Inventory supported pseudo-class arguments and their browser support, then verify that the resulting compatibility data distinguishes each requested case and reflects the documented restrictions.

Written by the indexing model from the issue text.

Assessment

Tech stack
css
Domain
frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.