5 ms·
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" dif
by polotics 2y 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...
- jeroenhd 2y agoThis 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.
- amiga386 2y agoThe 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 https://caniuse.com/url-scroll-to-text-fragment [1] https://whattrainisitnow.com/calendar/ https://whattrainisitnow.com/calendar/
- nanna 2y agoWhich is to say, that it work on Firefox.
- amiga386 2y agoI'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.
- master-lincoln 2y agoWhat? 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.
- amiga386 2y agoI'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"
- master-lincoln 2y agoIs there an alternative? Do users with browser that don't have support have a worse experience when these links are used? I thought no...
- amiga386 2y agoAs an alternative, all browsers the traditional scrolling to named element using a URL fragment, e.g. https://en.wikipedia.org/wiki/URI#Syntax https://en.wikipedia.org/wiki/URI#Syntax goes to the "Syntax" section of the page. While the reason of text fragments it to allow for similar linking where there isn't an element with an id, most pages with non-changing text tend also to have non-changing layout and element ids. If you generate links that include and depend on #:~:text= to make sense, accept that it will confuse users whose browsers do not support it. They will be linked to the top of the document and no text will be highlighted. Consider not only linking, but also quoting what you wanted to be highlighted, e.g. John says <a href="https://example.com/#:~:text=I%20dislike%20this">he dislikes it</a>: <blockquote cite="https://example.com/"> Down with this sort of thing. <em>I dislike this</em> and can't abide it. </blockquote>
- deleted 2y ago[deleted]
- newswasboring 2y ago> 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?
- reportgunner 2y agoSomething with internet explorer but I'm not old enough to know what exactly.
- xp84 2y agoI 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.
- milliams 2y agoIt 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".
- rzzzt 2y agoEdge does have a "Copy link to highlight" option in its context menu.
- nashashmi 2y agoAnd on mobile, it is called “create link”
- arp242 2y agoIt was added to Firefox in 131, released a few weeks ago: https://www.mozilla.org/en-US/firefox/131.0/releasenotes/ 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.
- amiga386 2y agoFYI, the "standard doc" isn't in any sense standardised yet https://wicg.github.io/scroll-to-text-fragment/ 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.
- ruthmarx 2y agoIsn'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?
- amiga386 2y agoNo, I would say you were describing WHATWG and their HTML5 specification (now called the HTML Living Standard) https://en.wikipedia.org/wiki/WHATWG 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 https://www.w3.org/community/wicg
- ruthmarx 2y agoOh yeah I got that mixed up. Thanks.