This shouldn’t be a big deal unless they go out of their way to use non-standard Chrome-only features.
It’s not like the early 2000s where you absolutely had to test everything on every browser because they differed so much and everyone was adding random non-standard features. I haven’t ran into something that doesn’t work on Firefox in quite a long time, even when all the development happens on Chrome.
Pretty much everything these days ends up through babel and automatic polyfills and browserlists. Unless they have a whole custom framework that somehow directly uses Chrome-specific APIs it’s unlikely Firefox will be left unusable. They have to deal with Safari regardless, and if Safari works, Firefox probably does. Safari is like the new IE these days in terms of bugs and missing standard features, and because you’re forced to use Safari on iOS, and iPhones are so popular, I seriously doubt they’d drop Safari either.
This shouldn’t be a big deal unless they go out of their way to use non-standard Chrome-only features.
It’s not like the early 2000s where you absolutely had to test everything on every browser because they differed so much and everyone was adding random non-standard features. I haven’t ran into something that doesn’t work on Firefox in quite a long time, even when all the development happens on Chrome.
Pretty much everything these days ends up through babel and automatic polyfills and browserlists. Unless they have a whole custom framework that somehow directly uses Chrome-specific APIs it’s unlikely Firefox will be left unusable. They have to deal with Safari regardless, and if Safari works, Firefox probably does. Safari is like the new IE these days in terms of bugs and missing standard features, and because you’re forced to use Safari on iOS, and iPhones are so popular, I seriously doubt they’d drop Safari either.