- From: Jerry Green via GitHub <sysbot+gh@w3.org>
- Date: Tue, 20 Feb 2024 19:15:53 +0000
- To: public-css-archive@w3.org
Until someone gives me an example where `history.back()` and `history.forward()` should respect `:target`, while `history.pushState()` and `history.replaceState()` shouldn’t – I advocate for all of them to handle the `:target` the same way. The current browsers behavior in this regard, is awful. It’s so inconsistent, so surprising. If current spec says otherwise, the spec is awful too. Prove me wrong. The current approach almost says to me: «don’t touch browser's native `:target`, make your own target implementation with javascript and classes, leave this pseudo-class alone, it’s messed up, and please make your own history object just like React does»… Heck, should I make my own browser too, in such a case? Gosh… -- GitHub Notification of comment by jerrygreen Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6942#issuecomment-1954896421 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 20 February 2024 19:15:54 UTC