Hacker News new | ask | show | jobs
by polotics 606 days ago
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...
5 comments

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?
No, I would say you were describing WHATWG and their HTML5 specification (now called the HTML Living Standard)

https://en.wikipedia.org/wiki/WHATWG

The Web Platform Incubator Community Group is "a lightweight venue for proposing and discussing new web platform features" within the W3C

https://www.w3.org/community/wicg

Oh yeah I got that mixed up. Thanks.
Edge does have a "Copy link to highlight" option in its context menu.
And on mobile, it is called “create link”
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.
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.

What? It is there already in Firefox latest version. Do you mean it will take that long until the majority of users have it?

If you decide to not update or use a version that is updated less often, that is not the fault of the people working on the software.

Be honest and admit that you are knowingly using a Firefox version that gets major updates only every 52 weeks and still complain about not getting a released feature.

I'm not complaining. What I'm trying to highlight is, as it says on the caniuse.com page, this feature has "Limited availability across major browsers", and that is to be expected and accepted.

If you're thinking of promoting use of this non-standard feature, consider how many people it _doesn't_ work for, rather than thinking "oh and yes even Firefox (asoftendaysagoandonlythedesktopmainlinereleasenottheesrormobileversion) so I'll rush out and proseletyze this amazing feature that clearly everyone can use"

> If you decide to not update

Browser support isn’t about what version you personally decide to run, it’s about what version your users are running. What Firefox ESR supports is the relevant factor here.

> Be honest and admit

Can you make your point without accusing people of dishonesty?

It works just fine on Firefox. The things that seems to be Chrome-only is the "select some text, right click to get direct link" bit, and the "link to text that is hidden".
> 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...

Can you elaborate on this a bit?

I think GP mistakenly believes that Chrome implemented this in its proprietary part instead of getting it from Chromium which was the actual case. In reality I think the feature appeared in both browsers at roughly the same time as a result.

And also that they believe that adding features like this to browsers is bad behavior in the first place. If that were the case and people abided by the "do nothing until the W3C acts" rule we'd probably all be using IE6-level browsers still.

Something with internet explorer but I'm not old enough to know what exactly.