2 ms·
Confused. As I understand it, anything after the # in a uri isn't sent over the wire. So the only way someone could see that you're navigating to a specific f
by tyingq 7y ago
Confused. As I understand it, anything after the # in a uri isn't sent over the wire.
So the only way someone could see that you're navigating to a specific fragment is some sort of deep chrome logging, or chrome plugin, etc. And if that's the case, cat's already out of the bag for everything you do already.
- hesselink 7y agoI was confused as well. I think (from some other comments) that the issue is that you can scroll to text that is specific to you and others might not have on their page (e.g. 'cancer' on some medical page) and then somehow gather from the requests that you scrolled there. It seems pretty hypothetical, but I can see the issue with forcing a scroll depending on what text is on the page, I guess.