Live data from Hacker News

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

alfy.blog

11–20 of 145 posts

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

#12
post #3

Very nice! Hopefully Firefox developers have the bandwidth to implement this as well, and not let Google Chrome have this feature as an "embrace and extend" differentiator. As for MS-Edge, well I guess it must be funny for Microsoft to see they're getting a taste of their own sweet old medicine...

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.

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

#13
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...

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

#14
post #5

Earlier quoted context omitted.

This feature seems to work on Firefox as far as I can tell. It used to be one of those Chrome APIs, but now every browser but Safari seems to support them completely. I'm sure the Safari team can quickly implement the last bit of Javascript API when they get the opportunity to.

The feature "seems to work on Firefox" if you're using the version of Firefox released 10 days ago [0] It's not implemented in Firefox ESR and won't be until June 2025 [1] [0] https://caniuse.com/url-scroll-to-text-fragment [1] https://whattrainisitnow.com/calendar/

Which is to say, that it work on Firefox.

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

#16
post #14

Earlier quoted context omitted.

The feature "seems to work on Firefox" if you're using the version of Firefox released 10 days ago [0] It's not implemented in Firefox ESR and won't be until June 2025 [1] [0] https://caniuse.com/url-scroll-to-text-fragment [1] https://whattrainisitnow.com/calendar/

Which is to say, that it work on Firefox.

I'm running Firefox right now. It doesn't work. I use Firefox ESR version. Many people do. Many people have also not installed updates released a mere 10 days ago.

Be honest and admit that full, reliable support for this feature among all the main browsers is not going to be there until at least next year.

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

#18

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

Small tip, and I know it doesn't make it much better, but in few cases I've seen this done (Discourse is the main culprit and it's widely used) pressing Ctrl+F a second time will go to the normal browser "Search in this page" function. Still annoying, but manageable.

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

#20
post #12
post #3

Very nice! Hopefully Firefox developers have the bandwidth to implement this as well, and not let Google Chrome have this feature as an "embrace and extend" differentiator. As for MS-Edge, well I guess it must be funny for Microsoft to see they're getting a taste of their own sweet old medicine...

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.

Post reply on HN