3 ms·

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 compl

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.

amiga386 2y ago
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 https://caniuse.com/url-scroll-to-text-fragment [1] https://whattrainisitnow.com/calendar/ https://whattrainisitnow.com/calendar/
- nanna 2y ago
  Which is to say, that it work on Firefox.
  - amiga386 2y ago
    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.
    - master-lincoln 2y ago
      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.
      - amiga386 2y ago
        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"
        master-lincoln 2y ago
        Is 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 ago
        As 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>
      - JimDabell 2y ago
        > 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?
deleted 2y ago
[deleted]

amiga386 2y ago

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 https://caniuse.com/url-scroll-to-text-fragment [1] https://whattrainisitnow.com/calendar/ https://whattrainisitnow.com/calendar/

nanna 2y ago
Which is to say, that it work on Firefox.
- amiga386 2y ago
  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.
  - master-lincoln 2y ago
    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.
    - amiga386 2y ago
      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"
      - master-lincoln 2y ago
        Is 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 ago
        As 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>
    - JimDabell 2y ago
      > 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?

deleted 2y ago

[deleted]