Wednesday, July 6, 2022
HomeiOS DevelopmentLinking to textual content fragments in net pages – Ole Begemann

Linking to textual content fragments in net pages – Ole Begemann


Textual content fragments are a manner for net hyperlinks to specify a phrase or phrase a browser ought to spotlight on the vacation spot web page. Google Chrome added help for them in model 80 (launched in February 2020).

For instance, opening the hyperlink oleb.web/2020/swift-docker-linux/#:~:textual content=operating,container in Chrome ought to spotlight the primary heading of the article:



Chromium highlighting the textual content fragment specified within the URL.

The apparent use case is search engines like google: whenever you click on a hyperlink in a search outcome, the browser would routinely spotlight your search time period(s) on the vacation spot web page.

I’ve all the time needed this characteristic. I typically discover myself visiting a web page from a search engine, solely to right away hit Cmd+F and re-type my search question into the browser’s Discover on Web page textual content area. Evidently, this can be a ache on cell units with no correct keyboard.

However textual content fragments produce other makes use of past search engines like google:

  1. Linking to a selected sentence or paragraph of an extended doc. I’d use this on a regular basis when linking to API documentation or discussion board posts. “Regular” URL fragments solely work for anchors the creator of the vacation spot web page created upfront, and readers normally can’t see what anchor tags can be found on a web page.

  2. Sharing a particular portion of a web page. Browsers might facilitate this by providing to incorporate a textual content fragment within the URL when sharing a hyperlink to a textual content choice.

Right here’s the pattern URL from above as soon as extra:


https://oleb.web/2020/swift-docker-linux/#:~:textual content=operating,container

This half is the textual content fragment:


#:~:textual content=operating,container

This fragment finds the primary point out of “operating” (case-insensitive) on the web page and highlights all the pieces from that time till it finds “container”. There are just a few extra variants of the syntax. Learn the textual content fragments draft spec for particulars.

Search phrases could comprise delicate data that customers don’t wish to share with the vacation spot server. For good motive, search engines like google stopped reporting the person’s search phrases within the referer header a very long time in the past as a part of the widespread transfer to HTTPS. It could be dangerous if a brand new characteristic reintroduced this outdated information leak.

The spec considers this problem. Textual content fragments are designed to be purely a browser-level characteristic — they’re not uncovered to JavaScript code. This screenshot demonstrates that doc.location.hash is clean as a result of Chromium stripped the textual content fragment away:


Screenshot of the JavaScript console in Chromium demonstrating that the destination page can’t see the text fragment
JavaScript code operating within the vacation spot web page can’t see the textual content fragment.

I feel this the correct habits, however the spec authors appear to be contemplating altering it again as a result of it might constrain some official use circumstances and since JavaScript can already decide what parts of a web page a person is studying by monitoring the viewport rect. I don’t know — exposing a delicate search time period appears extra invasive to me than the scroll place.

It’s price noting that the privateness concern exists for browsers that don’t help textual content fragments: they may deal with the gibberish as a standard URL fragment, which may simply be parsed with a little bit of JavaScript.

As a precaution, search engines like google and comparable websites ought to in all probability solely embrace textual content fragments of their hyperlinks if the person’s browser helps the characteristic (window.location.fragmentDirective).

Chrome is at present the one browser with textual content fragment help. From what I’ve learn, the WebKit and Firefox groups are usually supportive of the thought however have some reservations about particular design selections.

I hope this or one thing prefer it turns into extensively supported within the close to future.

Replace June 22, 2020: I uncared for to say fragmentations, an IndieWeb initiative that goals to unravel the identical drawback and is at the very least six years outdated. This characteristic makes use of regular URL fragments and client-side JavaScript to search out the matching textual content on the vacation spot web page (which is simply crucial as a result of there’s no native browser help, in fact).

RELATED ARTICLES

LEAVE A REPLY

Please enter your comment!
Please enter your name here

- Advertisment -
Google search engine

Most Popular

Recent Comments