- From: fantasai via GitHub <sysbot+gh@w3.org>
- Date: Fri, 06 May 2022 23:18:39 +0000
- To: public-css-archive@w3.org
Afaict, the Selectors spec has always defined the :target element in terms of the currently-effective fragment ID. (Selectors does not have a concept of history, so it is always evaluated against the current state of the document.) So I would push back against this issue and say, are we *really sure* that it's not Web-compatible to do the right thing here? Because that seems like the best way forward. I'd rather not introduce a new `:target-no-really` pseudo-element that everyone has to learn, alongside learning the fact that `:target` itself is broken. -- GitHub Notification of comment by fantasai Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6942#issuecomment-1120071405 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 6 May 2022 23:18:40 UTC