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

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

From: Brian Kardell via GitHub <sysbot+gh@w3.org>
Date: Fri, 27 Mar 2020 17:00:37 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-605113601-1585328436-sysbot+gh@w3.org>
Just want to agree with @andruud here that I am a little unconvinced that these are not confused in the poll and overlapping.  I asked this back in Feb, connected by them via twitter on just [how it was even worded?](https://github.com/StateOfJS/StateOfCSS-2019/issues/53) but didn't get any reply.  In most of my conversations, by parent selector, many people seem to have different interpretations

- some think this means `<` instead of just `>' which is just "change the direction of matching" and... that's kind of more than even has because you could switch all over.
- some thinks this means some variant of a `:has` proposal (any ancestor)
- some thinks it means literally parent, but don't think it has any limits

I'm just one person tho, and understand that's all anecdotal. 

It's also not to say that something very limited has no use... It feels worth a nice post explaining a proposal and its limits and getting feedback from devs though first?

-- 
GitHub Notification of comment by bkardell
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4903#issuecomment-605113601 using your GitHub account
Received on Friday, 27 March 2020 17:00:44 UTC

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