> Take the hours spent on this "innovation" and instead implement a feature that Chrome has which Firefox doesn't.
I think a better approach is to implement a feature that Chrome doesn't have. Their current approach is to make FF a clone of Chrome which just means that there are very few compelling reasons to use FF over Chrome.
If they don't have an idea for such a feature, I'd suggest implementing a feature which FF had and Chrome doesn't - bring back the ability for extensions to modify the browser's UI elements. If all they can think of to do with their UI is to make it a clone of Chrome's, why not let someone else come up with something cool? I'd love to at least get the old search box back if nothing else (what at some point was still possible by setting showOneOff to false)
I'd be over the moon if they tried to outdo chrome as long as they keep to UI stuff instead of web features.
Unfortunately with firefox being so far behind in terms of adoption all features they add in terms of the web content or JavaScript which aren't in chrome are DOA.
It's unfortunately a similar story for extensions. Power user stuff is great but success in firefox will depend on the browser having features directly and really nailing down making those work well and be intuitive for the average person.
Also bug fixes. All the bug fixes. Especially on Android, which I abandoned thanks to their PWAs not quite working right.
I think a better approach is to implement a feature that Chrome doesn't have. Their current approach is to make FF a clone of Chrome which just means that there are very few compelling reasons to use FF over Chrome.
If they don't have an idea for such a feature, I'd suggest implementing a feature which FF had and Chrome doesn't - bring back the ability for extensions to modify the browser's UI elements. If all they can think of to do with their UI is to make it a clone of Chrome's, why not let someone else come up with something cool? I'd love to at least get the old search box back if nothing else (what at some point was still possible by setting showOneOff to false)