HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
bokand
ScrollToTextFragment
HTML2019–2019
bokand / ScrollToTextFragment

ScrollToTextFragment

Proposal to allow specifying a text snippet in a URL fragment

3Distinct people
5Mentions
0Explicit recommenders
14GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Proposal to allow specifying a text snippet in a URL fragment

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 4:59:52 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by hour5 dated mentions

Observed mentions: 2019-02-15 07:04:15 UTC to 2019-02-15 17:10:36 UTC.

0122019-02-15 07:00:00 UTC to 2019-02-15 08:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsFeb 15, 07:002019-02-15 08:00:00 UTC to 2019-02-15 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-02-15 09:00:00 UTC to 2019-02-15 10:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-02-15 10:00:00 UTC to 2019-02-15 11:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2019-02-15 11:00:00 UTC to 2019-02-15 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-02-15 12:00:00 UTC to 2019-02-15 13:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsFeb 15, 12:002019-02-15 13:00:00 UTC to 2019-02-15 14:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-02-15 14:00:00 UTC to 2019-02-15 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-02-15 15:00:00 UTC to 2019-02-15 16:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2019-02-15 16:00:00 UTC to 2019-02-15 17:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-02-15 17:00:00 UTC to 2019-02-15 18:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsFeb 15, 17:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Feb 15, 07:002019-02-15 07:00:00 UTC2019-02-15 08:00:00 UTC101
Feb 15, 08:002019-02-15 08:00:00 UTC2019-02-15 09:00:00 UTC000
Feb 15, 09:002019-02-15 09:00:00 UTC2019-02-15 10:00:00 UTC000
Feb 15, 10:002019-02-15 10:00:00 UTC2019-02-15 11:00:00 UTC101
Feb 15, 11:002019-02-15 11:00:00 UTC2019-02-15 12:00:00 UTC000
Feb 15, 12:002019-02-15 12:00:00 UTC2019-02-15 13:00:00 UTC000
Feb 15, 13:002019-02-15 13:00:00 UTC2019-02-15 14:00:00 UTC000
Feb 15, 14:002019-02-15 14:00:00 UTC2019-02-15 15:00:00 UTC000
Feb 15, 15:002019-02-15 15:00:00 UTC2019-02-15 16:00:00 UTC202
Feb 15, 16:002019-02-15 16:00:00 UTC2019-02-15 17:00:00 UTC000
Feb 15, 17:002019-02-15 17:00:00 UTC2019-02-15 18:00:00 UTC101

What Hacker News says

1 sources
At first glance, this seems like a really half baked idea to me. Some immediate thoughts: - Wasn't there a draft spec floating around in the early 00s that tried to accomplish this, but didn't catch on? - Fragments are already used to link to fragments, albeit more author friendly than user friendly I suppose - This won't fly very well with sites that still make use of fragment based navigation, will it? (Believe it or not, I still see new projects use this over the history API!) - What happens if there's an element in a page with the id or name `targetText`? This is not mentioned in the very tiny compatibility section[1] (where some actual data wouldn't hurt, btw) - The linked proposal[2] already mentions that more specific fragment semantics is defined in other media types, so why not follow suit and propose the HTML spec is amended, in
Read the rest
stead of making this a user agent feature? - Fragments in URLs are already pretty useless in sites that don't load content until after the dom is ready, i.e. anything that just loads a bunch of JS and then builds the site in the client – how would this fare any better? [1]: https://github.com/bokand/ScrollToTextFragment#web-compatibi... [2]: https://github.com/bokand/ScrollToTextFragment#encoding-the-...
In Chrome will Soon Let You Share Links to a Specific Word or Sentence on a Page

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.