Yeah, I’m also a web developer and this person is completely up their own ass. We’ve all struggled with browsers that lag behind standards (internet explorer) or implement them in weird ways (safari). But Mozilla has never even come close to being a problem like the others.
Also I doubt they are using the newest of new web standards that would actually need to be poly filled and even then with modern JS build tooling poly filling isn’t difficult or abnormal. Oh, the bundle for your crappy SPA might be a few kb bigger but that isn’t gonna make a difference.
[This comment has been deleted by an automated system]
Yeah, I’m also a web developer and this person is completely up their own ass. We’ve all struggled with browsers that lag behind standards (internet explorer) or implement them in weird ways (safari). But Mozilla has never even come close to being a problem like the others.
Also I doubt they are using the newest of new web standards that would actually need to be poly filled and even then with modern JS build tooling poly filling isn’t difficult or abnormal. Oh, the bundle for your crappy SPA might be a few kb bigger but that isn’t gonna make a difference.
Side panel, workspaces, tab-stacking, just to name a few.
[This comment has been deleted by an automated system]
“What major standard features is Firefox missing these days?”
This was your question, nowhere did you say anything about web API’s. You stupid or just forget which comment I was responding to?
Sure FF has extensions that “kinda do the same thing” except they’re shit and bloat the browser beyond what it already is compared to Vivaldi.
[This comment has been deleted by an automated system]
To name a big one: the CSS :has() pseudo-class.
How is this still not enabled by default?
[This comment has been deleted by an automated system]