>We'll keep support for MV2 extensions for as long as possible.
This doesn't particularly give people any confidence in your product if even the devs don't know how long they can hold the line.
Why not fork Firefox like Zen?
I know this is unfair to firefox, majority of enterprise software now (including and starting with Microsoft teams) outright say do not support firefox or have ‘limited’ support whatever that means.
For anyone working remotely like me, teams is a crucial piece of software (however bad it is). So as much as I like Firefox and legends that started it and religiously developed it over the years, bottom line, I can’t use it now.
Some maybe majority of blame falls on Mozilla, they let it stagnate and focus on cosmetic changes in last few years instead of focusing on improving core technology.
> majority of enterprise software now (including and starting with Microsoft teams) outright say do not support firefox
Teams has explicitly supported Firefox for a while now https://learn.microsoft.com/en-us/microsoftteams/teams-clien... but the problem is "there's always another site that doesn't work right". Firefox usage share got too low, so places just check Chrom* and Safari work with the new feature and ship (sometimes not even the latter, if they don't care about mobile as much).
Feels like we need something like early versions of Edge, where it was using Chromium but could be told to open individual tabs (or configured to always open links to certain origins) in an IE webview.
Except, instead of Chromium, Firefox, and instead of IE, Chromium.
Many vendors look at the userAgent. I’d be surprised if Microsoft Teams org doesn't have some soft incentives pushing Edge and if not edge Chromium-based browsers.
Then again, there are definitely some Firefox behaviors that differ from the WebKit-derived engines (webkit, blink, etc); for a few years Notion editor had very different UX in Firefox for this reason. They eventually fixed it though! Firefox's profiler is also excellent, I always analyze my Chrome profiles in https://profiler.firefox.com/ when I'm optimizing CPU use.
indiebat|5 months ago
For anyone working remotely like me, teams is a crucial piece of software (however bad it is). So as much as I like Firefox and legends that started it and religiously developed it over the years, bottom line, I can’t use it now.
Some maybe majority of blame falls on Mozilla, they let it stagnate and focus on cosmetic changes in last few years instead of focusing on improving core technology.
zamadatix|5 months ago
Teams has explicitly supported Firefox for a while now https://learn.microsoft.com/en-us/microsoftteams/teams-clien... but the problem is "there's always another site that doesn't work right". Firefox usage share got too low, so places just check Chrom* and Safari work with the new feature and ship (sometimes not even the latter, if they don't care about mobile as much).
derefr|5 months ago
Except, instead of Chromium, Firefox, and instead of IE, Chromium.
jitl|5 months ago
Then again, there are definitely some Firefox behaviors that differ from the WebKit-derived engines (webkit, blink, etc); for a few years Notion editor had very different UX in Firefox for this reason. They eventually fixed it though! Firefox's profiler is also excellent, I always analyze my Chrome profiles in https://profiler.firefox.com/ when I'm optimizing CPU use.
yeasku|5 months ago
Citrix has always been shit, so is not surprising.
hooverd|5 months ago
chneu|5 months ago