▲ 1729 ▼ Why Bother With uBlock Being Blocked In Chrome? Now Is The Best Time To Switch To Firefox (tuta.com) submitted 2 years ago by L4s@lemmy.world [M, B] to c/technology@lemmy.world 314 comments fedilink hide all child comments Why Bother With uBlock Being Blocked In Chrome? Now Is The Best Time To Switch To Firefox::Choose the browser that best suits your privacy needs.
[+] Xylight@lemdro.id 28 points 2 years ago* (last edited 1 year ago) (4 children) [deleted] permalink fedilink source hideshow 8 child comments replies: [–] AlphaOmega@lemmy.world 7 points 2 years ago (2 children) I haven't had any issues with browser compatibility since IE. Occasionally Safari might have some CSS issue, but it's been probably 10 years since I had any major issues with browser compatibility. Html 5 and CSS 3 tend to work across all browsers without issue. permalink fedilink source parent hideshow 4 child comments replies: [–] smileyhead@discuss.tchncs.de 1 point 2 years ago* (2 children) Across all two of them. I would really like to see how broken the web would be if someone in theory create a new complete implementation of the basic standards. permalink fedilink source parent hideshow 4 child comments replies: [–] bamboo@lemm.ee 1 point 2 years ago Three: Chrome and friends, Safari, Firefox permalink fedilink source parent [+] nix@midwest.social 1 point 2 years ago [deleted] permalink fedilink source parent [–] offspec@lemmy.nicknakin.com 1 point 2 years ago There are some niche features Mozilla refuses to accept like WebSerial and WebMIDI, but they're starting to come around on them. permalink fedilink source parent [–] Contend6248@feddit.de 7 points 2 years ago Well the market share is the whole story when it comes figuring out whats the standard permalink fedilink source parent [–] redditReallySucks@lemmy.dbzer0.com 5 points 2 years ago I think devs go chrome first and then adapt the site to firefox. permalink fedilink source parent [–] TCB13@lemmy.world 4 points 2 years ago (1 child) Because Chrome rendering and dev tools are effetely superior to Firefox. That's why. permalink fedilink source parent hideshow 2 child comments replies: [–] RustyNova@lemmy.world 1 point 2 years ago I'd disagree on Dev tools. Both are really great and useful. What I'd say is that Firefox may have less support for external debugging, but that's more others choosing not to do Firefox debugging permalink fedilink source parent
[–] AlphaOmega@lemmy.world 7 points 2 years ago (2 children) I haven't had any issues with browser compatibility since IE. Occasionally Safari might have some CSS issue, but it's been probably 10 years since I had any major issues with browser compatibility. Html 5 and CSS 3 tend to work across all browsers without issue. permalink fedilink source parent hideshow 4 child comments replies: [–] smileyhead@discuss.tchncs.de 1 point 2 years ago* (2 children) Across all two of them. I would really like to see how broken the web would be if someone in theory create a new complete implementation of the basic standards. permalink fedilink source parent hideshow 4 child comments replies: [–] bamboo@lemm.ee 1 point 2 years ago Three: Chrome and friends, Safari, Firefox permalink fedilink source parent [+] nix@midwest.social 1 point 2 years ago [deleted] permalink fedilink source parent [–] offspec@lemmy.nicknakin.com 1 point 2 years ago There are some niche features Mozilla refuses to accept like WebSerial and WebMIDI, but they're starting to come around on them. permalink fedilink source parent
[–] smileyhead@discuss.tchncs.de 1 point 2 years ago* (2 children) Across all two of them. I would really like to see how broken the web would be if someone in theory create a new complete implementation of the basic standards. permalink fedilink source parent hideshow 4 child comments replies: [–] bamboo@lemm.ee 1 point 2 years ago Three: Chrome and friends, Safari, Firefox permalink fedilink source parent [+] nix@midwest.social 1 point 2 years ago [deleted] permalink fedilink source parent
[–] bamboo@lemm.ee 1 point 2 years ago Three: Chrome and friends, Safari, Firefox permalink fedilink source parent
[–] offspec@lemmy.nicknakin.com 1 point 2 years ago There are some niche features Mozilla refuses to accept like WebSerial and WebMIDI, but they're starting to come around on them. permalink fedilink source parent
[–] Contend6248@feddit.de 7 points 2 years ago Well the market share is the whole story when it comes figuring out whats the standard permalink fedilink source parent
[–] redditReallySucks@lemmy.dbzer0.com 5 points 2 years ago I think devs go chrome first and then adapt the site to firefox. permalink fedilink source parent
[–] TCB13@lemmy.world 4 points 2 years ago (1 child) Because Chrome rendering and dev tools are effetely superior to Firefox. That's why. permalink fedilink source parent hideshow 2 child comments replies: [–] RustyNova@lemmy.world 1 point 2 years ago I'd disagree on Dev tools. Both are really great and useful. What I'd say is that Firefox may have less support for external debugging, but that's more others choosing not to do Firefox debugging permalink fedilink source parent
[–] RustyNova@lemmy.world 1 point 2 years ago I'd disagree on Dev tools. Both are really great and useful. What I'd say is that Firefox may have less support for external debugging, but that's more others choosing not to do Firefox debugging permalink fedilink source parent