Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Smarter Than 'Ctrl+F': Linking Directly to Web Page Content

alfy.blog

Post reply on HN
Print view View original

111–120 of 145 posts

Re: Smarter Than 'Ctrl+F': Linking Directly to Web Page Content

#111

Post by KTibow »

gertrunde wrote: post #103

In all honesty, I've hated this feature with a passion ever since it appeared. If it was simply a matter of being used in the way outlined in the article, when someone creates a a link that references a particular piece of text, then fine, someone has deliberated intended the link to behave like that. And then we have the lovely folk at Google search... who think it's fun to drag my attention off to a random part of…

That sounds annoying, even if the only work required was to press `Home`. Does this only happen with the featured snippets?

Re: Smarter Than 'Ctrl+F': Linking Directly to Web Page Content

#112

Post by c-linkage »

rakoo wrote: post #94

Unsurprisingly this is something you could do in Plan 9: /path/to/file:/from.*to opens the file and sets the selection to the range of text between "from" and "to". Bonus: you can use regular expressions. It pains me to see the web having strayed so far from its focus on interlinking. It's easy to make a parallel when on one side device makers have taken control back by removing access to files and putting applicatio…

The world wide web has moved beyond documents to apps. With apps there is nothing left to interlink.

Re: Smarter Than 'Ctrl+F': Linking Directly to Web Page Content

#115

Post by taco_emoji »

RedShift1 wrote: post #2

Sidenote: please don't hijack CTRL+F on webpages, thanks. Sincerely, the world.

Sometimes it's fine if a page is lazy-loading content, in which the browser's CTRL+F does not work because the text isn't all in the DOM at that moment.

Re: Smarter Than 'Ctrl+F': Linking Directly to Web Page Content

#117

Post by kenrick95 »

lolinder wrote: post #73

Today I learned that Firefox finally implemented these! They don't mention this in the article, but that's new this month—for the longest time Chrome supported it but it isn't in the standard and Firefox didn't include it. Safari got it 2 years later, but Firefox held out for a while. I'm normally not a fan of Chrome unilaterally adding something to the platform, but this has been a long time coming.

I was surprised too, cause initially they had some issues with the proposal [1], resolved it few years later [2], and finally implemented it since last year [3]

[1] https://github.com/mozilla/standards-positions/issues/194#is...

[2] https://github.com/mozilla/standards-positions/issues/194#is...

[3] https://bugzilla.mozilla.org/show_bug.cgi?id=1753933

Re: Smarter Than 'Ctrl+F': Linking Directly to Web Page Content

#118

Post by Kerrick »

shakna wrote: post #58
fbn79 wrote: post #38

In Google Chrome select text, right click and click "copy link to highlight". It create a link with ~:text=

Also added to the next release for Firefox.

Also works in Orion, though it's labeled "Copy link to selection."

Re: Smarter Than 'Ctrl+F': Linking Directly to Web Page Content

#119

Post by dbodin11 »

This is the ultimate time saver feature when sharing. I built a web layer that does this, but goes further with multiple highlights, navigation, and rich inline communication with humans and AI, which is integrated with a web app to save, organize, and share with humans and AI. It’s https://www.kontxt.io

Re: Smarter Than 'Ctrl+F': Linking Directly to Web Page Content

#120

Post by ruthmarx »

amiga386 wrote: post #20
arp242 wrote: post #12

Earlier quoted context omitted.

It was added to Firefox in 131, released a few weeks ago: https://www.mozilla.org/en-US/firefox/131.0/releasenotes/ And "add useful UX features that people want" is not "EEE", especially when there's a standard doc and test suite for it.

FYI, the "standard doc" isn't in any sense standardised yet https://wicg.github.io/scroll-to-text-fragment/ > This specification was published by the Web Platform Incubator Community Group. It is not a W3C Standard nor is it on the W3C Standards Track.

Isn't Web Platform Incubator Community Group the group browsers makers formed because the W3C was being too slow and then largely overtook the W3C in terms of relevance?
Post reply on HN