- From: Byungwoo Lee via GitHub <sysbot+gh@w3.org>
- Date: Wed, 09 Jun 2021 02:26:48 +0000
- To: public-css-archive@w3.org
I recently started prototyping ':has()' pseudo class in Chrome, and there was [a mailing thread](https://groups.google.com/a/chromium.org/g/blink-dev/c/hqkcKdDrhXE/m/i2ADPY78AQAJ) about the interaction of ':has()' and ':visited' in terms of privacy issues. Although the ':visited' discussion seems to be going on in another thread, and the ':has()' prototyping is very early stage, I thought it might be worth sharing the ':has()' related approach here because it is based on the current chrome ':visited' privacy approach. The current approach to privacy considerations for ':visited' in the ':has()' argument selector is: - The ':visited' selector does not match if it is inside the ':has()' argument selector to prevent leaking visitedness to the link's ancestors by ':has()'. So if a ':has()' argument selector requires a matching ':visited', the style rule will not be applied. -- GitHub Notification of comment by byung-woo Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2037#issuecomment-857321596 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 9 June 2021 02:27:28 UTC