W3C home > Mailing lists > Public > public-css-archive@w3.org > March 2020

Re: [csswg-drafts] [css-selectors] has-child selector (#4903)

From: Adam Argyle via GitHub <sysbot+gh@w3.org>
Date: Fri, 27 Mar 2020 23:05:02 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-605349998-1585350301-sysbot+gh@w3.org>
> Hopefully most of the respondents actually did mean parent (:has-child) and not ancestor (:has-descendant).
> @argyleink @una Do you have any gut feeling regarding this? 

From my experience folks exclusively mean ancestor querying. Eg, they want a child to own how it responds to a class or state findable further up the DOM. @bkardell had it right when using the `<` character, as a way of visualizing the intent `.dark < .my-component {...}`. I dont know anyone who's aware of `:has` when talking about this topic. 

GitHub Notification of comment by argyleink
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4903#issuecomment-605349998 using your GitHub account
Received on Friday, 27 March 2020 23:05:04 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:42:02 UTC