scroll-to-text-fragment

Brave has this feature disable due to (rather minor, imho) privacy concerns. https://github.com/WICG/scroll-to-text-fragment/issues/76 https://github.com/brave/brave-browser/issues/17994

Is there a specified / supported way to include other parameters in the URI fragment if the fragment part of the URI starts with :~:text=? https://example.com/page.html#:~:text=[prefix-,]textStart[,textEnd][,-suffix] https://example.com/page.html#:~:text=... https://example.com/page.html#:~:text=...&param2=two&:~:param3=three w3c/web-annotation#442: "Selector JSON to IRI/URI Mapping: supporting compound fragments so that SPAs work" (2019): https://github.com/w3c/web-annotation/issues/442 WICG/scroll-to-text-fragment#4: "Integration with W3C Web Annotations" (2019): https://github.com/WICG/scroll-to-text-fragment/issues/4#iss...

There were some privacy concerns, regarding leaking of user information: https://github.com/WICG/scroll-to-text-fragment/issues/76

"Do you like the browser bookmark manager?" https://news.ycombinator.com/item?id=24511454 : > Things I'd add to browser bookmark managers someday: > - Support for (persisting) bookmarks tags. From the post re: the re-launch of del.icio.us: https://news.ycombinator.com/item?id=23985623 >> "Allow reading and writing bookmark tags" https://bugzilla.mozilla.org/show_bug.cgi?id=1225916 >> Notes re: how [browser bookmarks with URI|str* tags] could be standardized with JSON-LD: https://bugzilla.mozilla.org/show_bug.cgi?id=1225916#c116 * *** WICG/scroll-to-text-fragment "Integration with W3C Web Annotations" https://github.com/WICG/scroll-to-text-fragment/issues/4 *** W3C Web Share API & W3C Web Target API https://news.ycombinator.com/item?id=30449716

It's call "Text Fragments", and it was introduced to Chrome more than one year ago. https://github.com/WICG/scroll-to-text-fragment I think it works in Chrome and Edge, but not in Firefox.

More detail on the spec - https://github.com/WICG/scroll-to-text-fragment/

More details at https://chromestatus.com/feature/4733392803332096 and https://github.com/WICG/scroll-to-text-fragment/

The extension uses a new URL fragment addition that Chrome has shipped: https://github.com/WICG/scroll-to-text-fragment so these links will work on any Chrome/Chromium-based browser. (in non-Chromium browsers without the extension the link will load but the fragment wont be recognized) The hope is that this is useful and adopted by other browser engines and links like this would eventually be interoperable.

https://github.com/WICG/scroll-to-text-fragment It's a new feature in Chrome 80 https://chromestatus.com/feature/4733392803332096

The first example links to an index page; it should probably link to the specific page itself. I suggest trying out ScrollToTextFragment https://github.com/WICG/scroll-to-text-fragment if you haven't already I know it was a little controversial and it's currently Chrome-only, but it might improve the UX for some people. Very cool, though!

This is called ScrollToTextFragment. See https://github.com/WICG/ScrollToTextFragment I think they just started doing this a few hours ago. I only noticed it in the "Featured Snippet" box. Edit: > I was surprised because Quora can’t know what the search result looked like and so doesn’t know which part of the text to highlight. Did Google at some point stop sending referer headers that include the query? The last time I checked (~10 years ago, admittedly), they did, which was often collected for analytics. Regardless, it's the browser doing the highlighting in this case, not the site itself.

Well, not spec, but proposed spec. [1] Driven by Google, but under the auspices of W3C. > The W3C haven't been in the driver's seat for a very long time now when it comes to web standards. That was exactly ghostpepper's point. [1] https://github.com/WICG/ScrollToTextFragment

The github issue has more actual examples. The important bit is the "looking for lower-on-the-page resources being requested." bit. You can't necessarily tell anything from that lone DNS request. But after loading the page, the user's browser will go on to send requests for elements on the page, and anything JS wants to grab based on position, which can be a channel for information. Example: 99% of your employees' DNS requests to the company health portal are followed by DNS requests to the image CDN a few milliseconds later. However 1 specific request to FakeCompanyHealth.com is immediately followed by a DNS request to MayoClinic.com, because it turns out the web page dynamically loads an iframe to contact the Mayo Clinic once you scroll to the Cancer subsection. You could then assume based on timing that this user clicked a cancer-speci