the general state of firefox suggests that they are not large enough to do more than one thing.
However, I did do a lot of frontend back in the old IE6/IE7/IE8 days when you essentially had to code a whole separate front end for Microsoft's standards-flaunting mess. So this is definitely an issue I care about.
but behind the curtains it took additional effort from
the developers of websites you visit to make it so
So yes, you often can't run your Chrome-specific shit elsewhere without workarounds and polyfills, but this doesn't automatically mean everybody except Google is screwing up. In some cases, complaints such as yours sound like folks in 2004 complaining that their ActiveX controls work in IE but not Firefox.
And not to forget that Google has even shipped several early-days standards track features to production of which the API was still in flux. In a few cases the API later changed in - for Chrome, at least - breaking ways. Fun times.
okay, but does mozilla have a good reason for not supporting that stuff other than "we have limited resources to implement these things"?
a lot of that chrome-specific shit is really really nice. like CSS nesting - that would be amazing. firefox has a bug for tracking the implementation, and supported the standardization of it. but there's no sign of any progress towards an implementation. meanwhile safari and chrome have both shipped it.
That depends on what you are referring to. No there is not a one size fits all answer. For example, Chrome has implemented Filesystem API that Mozilla is still debating on because they see it as a security issue. You can agree or disagree but there reason is still something other than "we don't have the resources to do it"
For example, Chrome has implemented Filesystem API
that Mozilla is still debating on
Google explicitly wants two major things from Chrome.
One, they obviously want to track as much personal information as they possibly can, because they are an ad company.
Two, they want "the web" to essentially be a full OS replacement, with filesystem access etc. Because Microsoft is one of their primary rivals (or frenemies, if you will) and they can't leave themselves to the whims of others' platforms. They need their own platform.
These goals are... well, let's say divergent (to put it mildly) from what "the web" means to others. HTTP was originally supposed to be a human-readable way to publish and link information, not an OS replacement, and certainly not a PII-siphoning tool.
And yet, some folks still default to simply assuming whatever Google decides for the web is right, simply because they seem to be moving the fastest.
Yeah, they're usually moving the fastest, but people should think about where they're heading and why.
If FF is lagging behind Safari on a particular CSS feature that certainly points to FF being behind the curve.
Sometimes it's FF or Safari simply being slower than Google. Sometimes it's a matter of the Chrome team creating an implementation of feature XYZ and getting it minted into the standard so of course they have the only implementation for a while.
Sometimes the FF and Safari teams have specific objections to a feature, often because unlike Google they actually consider user privacy a core part of their mission. Although, of course, with CSS features... that's not gonna be a privacy thing.
Android has native support for keyboards since API 1.
An iPad can support a keyboard too. It's a touch-first device.
A Mac can support a touchscreen with a third-party driver, but it's a KBM-first UX and support of the touchscreen is horrible in most apps that only accept one input at a time.
Will it drive worthwhile value? No.
Are there more pressing matters? Yes.
With that said, it's open source. Why don't you implement it yourself? Meanwhile the rest of us have long since moved on from Firefox.
Even the fully local translation is really usable now <3. I don't use chrome for anything and it's not even installed on my daily driver anymore.
Ironically, the only time I have had issues, overriding the user agent to look like chrome or edge fixed it. So those websites were deliberately broken with Firefox, not Mozilla's fault but pure malice and dark patterns. Office 365 is one of these sites by the way.
The issue here is that this wasn't always the case, or at least wasn't always this bad. While Firefox has always been far from perfect, there was a time when mozillazine consisted mostly of praise and evangelism, and not all of it naive fandom. Also, as a former Opera user, there was also a time when the landscape as a whole contained a higher quality set of options in general. There were numerous browsers then better than the current least worst.
Even recently, Firefox has inspired hope & interest with Servo, Quantum, and even things like the amazing webextension migration effort: controversial and unpopular with many it was nonetheless a greatly successful engineering effort, and has borne fruit in the recent furore over v3 manifests, with Firefox coming out ahead. It's also got cool added APIs that makes sense for the traditional Firefox community but are still standards compliant and interoperable. But all that progress is now already waning with Servo dev cut, progressive popular distinguishing features like MAC being relegated to APIs & UI removed from core.
There's precious little left to distinguish Firefox from Chrome, and nothing new on the horizon.
I'm pleased to see others have good experience with FF performance, but for me, the performance simply became unacceptable.
with their continued slide in marketshare to what is essentially an irrelevant portion of the market, i'm guessing this isn't just me.