4 ms·

If you haven't made the switch to Firefox, now is the time. There's no reason to keep supporting Google through Chrome. There hasn't been one in years.

tapoxi 2y ago
Chrome is faster for me, and I like tab grouping. uBlock Origin Lite is still supported. It theoretically has less features but I haven't noticed what they are.
- morserer 2y ago
  Firefox has multiple tab grouping extensions. And Mozilla independently checks the code of its top 3rd-party add-ons for safety.
  - tapoxi 2y ago
    They can't interact with the top tab bar after Mozilla switched to Webextension, so you're usually left with an awkward, secondary panel.
    - dredmorbius 2y ago
      The top tab bar in Firefox can be disabled: <https://support.mozilla.org/en-US/questions/1417387 https://support.mozilla.org/en-US/questions/1417387>
      - NoGravitas 2y ago
        It will pretty soon be possible to turn off top tabs in Firefox without this kind of userChrome jiggery-pokery. The sidebar API has been updated in Firefox Nightly 131, and it provides a side tab bar, and the ability to disable the top tab bar. Existing sidebar tab extensions will be able to update to this API.
        dredmorbius 2y ago
        That would be progress, thanks.
Terr_ 2y ago
It's bad for developers too, not just end-users. In particular, I recently ran into a very long-running issue where Chrom[ium] attempts to auto-fill inappropriate shit (like names from saved credit cards) into utterly unrelated form fields. This has been going on for many years now [0], because maintainers insist their browser must ignore standards like autocomplete="off" [1] and use some "crowdsourced" remote-server fuzzy-recognition bullshit, and when their AI system is terribly wrong there's way for pages to opt-out. This is especially aggravating for any developers who cannot meet WCAG accessibility guidelines that might be required of them by contract or law, and people have submitted a litany of other problematic examples [2] to no effect. _____________ [0] https://issues.chromium.org/issues/40093420 https://issues.chromium.org/issues/40093420 [1] https://source.chromium.org/chromium/chromium/src/+/main:components/autofill/core/common/autocomplete_parsing_util.h;l=50-52?q=autocomplete%20off&ss=chromium%2Fchromium%2Fsrc https://source.chromium.org/chromium/chromium/src/+/main:com... [2] https://issues.chromium.org/issues/41239842 https://issues.chromium.org/issues/41239842
- vaindil 2y ago
  I can't comment on all of Chrome's behavior here, but Firefox ignores autocomplete="off" too, and this is noted on MDN [0]. This is because a lot of poorly-managed sites think they're being security-conscious by disabling password managers, so browsers had to step in and ignore the attribute. [0] https://developer.mozilla.org/en-US/docs/Web/HTML/Attributes/autocomplete#off https://developer.mozilla.org/en-US/docs/Web/HTML/Attributes...
  - Terr_ 2y ago
    I don't have a problem with any browser supplying credentials that the user has already used and chosen to save for a specific particular domain/form/input. The issue is that Chrome is randomly/unpreventably suggesting all sorts of data even when field is for a medical patient's name rather than doctor using it, or when it's a generic chat-message field, and it does all that when the user has never used the form or even visited the domain before. Informing all customers that it's out of our hands and can only be stopped by disabling their personal Chrome settings is... Not practical.
feyman_r 2y ago
Firefox Containers by far is the best feature I’ve seen in a browser. For that alone, it’s worth trying it out in parallel. I moved from Chrome to Firefox 4 years ago over months; give it a shot - maybe move your social media browsing there.
deleted 2y ago
[deleted]

tapoxi 2y ago

Chrome is faster for me, and I like tab grouping. uBlock Origin Lite is still supported. It theoretically has less features but I haven't noticed what they are.

morserer 2y ago
Firefox has multiple tab grouping extensions. And Mozilla independently checks the code of its top 3rd-party add-ons for safety.
- tapoxi 2y ago
  They can't interact with the top tab bar after Mozilla switched to Webextension, so you're usually left with an awkward, secondary panel.
  - dredmorbius 2y ago
    The top tab bar in Firefox can be disabled: <https://support.mozilla.org/en-US/questions/1417387 https://support.mozilla.org/en-US/questions/1417387>
    - NoGravitas 2y ago
      It will pretty soon be possible to turn off top tabs in Firefox without this kind of userChrome jiggery-pokery. The sidebar API has been updated in Firefox Nightly 131, and it provides a side tab bar, and the ability to disable the top tab bar. Existing sidebar tab extensions will be able to update to this API.
      - dredmorbius 2y ago
        That would be progress, thanks.

Terr_ 2y ago

It's bad for developers too, not just end-users. In particular, I recently ran into a very long-running issue where Chrom[ium] attempts to auto-fill inappropriate shit (like names from saved credit cards) into utterly unrelated form fields. This has been going on for many years now [0], because maintainers insist their browser must ignore standards like autocomplete="off" [1] and use some "crowdsourced" remote-server fuzzy-recognition bullshit, and when their AI system is terribly wrong there's way for pages to opt-out. This is especially aggravating for any developers who cannot meet WCAG accessibility guidelines that might be required of them by contract or law, and people have submitted a litany of other problematic examples [2] to no effect. _____________ [0] https://issues.chromium.org/issues/40093420 https://issues.chromium.org/issues/40093420 [1] https://source.chromium.org/chromium/chromium/src/+/main:components/autofill/core/common/autocomplete_parsing_util.h;l=50-52?q=autocomplete%20off&ss=chromium%2Fchromium%2Fsrc https://source.chromium.org/chromium/chromium/src/+/main:com... [2] https://issues.chromium.org/issues/41239842 https://issues.chromium.org/issues/41239842

vaindil 2y ago
I can't comment on all of Chrome's behavior here, but Firefox ignores autocomplete="off" too, and this is noted on MDN [0]. This is because a lot of poorly-managed sites think they're being security-conscious by disabling password managers, so browsers had to step in and ignore the attribute. [0] https://developer.mozilla.org/en-US/docs/Web/HTML/Attributes/autocomplete#off https://developer.mozilla.org/en-US/docs/Web/HTML/Attributes...
- Terr_ 2y ago
  I don't have a problem with any browser supplying credentials that the user has already used and chosen to save for a specific particular domain/form/input. The issue is that Chrome is randomly/unpreventably suggesting all sorts of data even when field is for a medical patient's name rather than doctor using it, or when it's a generic chat-message field, and it does all that when the user has never used the form or even visited the domain before. Informing all customers that it's out of our hands and can only be stopped by disabling their personal Chrome settings is... Not practical.

feyman_r 2y ago

Firefox Containers by far is the best feature I’ve seen in a browser. For that alone, it’s worth trying it out in parallel. I moved from Chrome to Firefox 4 years ago over months; give it a shot - maybe move your social media browsing there.

deleted 2y ago

[deleted]