[montroser]

Overall, Firefox is wonderfully fantastic these days.

I can see how this is frustrating to some, but sometimes that's how the priority nets out. It looks like the bug was triaged, investigated, took its time finding its way to the right developers, and now a fix will land soon.

This is mostly just the process working. I for one, am grateful for these folks' good work.

[krsdcbl]

Yet this is a single example that actually was resolved, while far from the only inconsistencies and bugs.

While from an engine side, the situation with bugs lingering for years, and web features that still can't be used way, way after even Safari managed to implement them is not insignificant.

It's not broken or actually bad software, but it's struggling to keep up with the Browsers it's meant to be an independent alternative for.

This makes UX and feature parity a HUGE concern!

Loosing market share through inconveniencing users in turns means web devs will have increasingly less incentive to. work around it's quirks and issues, which even further shifts the Browser market towards a handful of huge, profit oriented companies - which is without exaggeration a threat to maintaining an open web.

[kelnos]

Yeah, if this was some bug that had been languishing for years without anyone caring to look at it, I'd consider this a stain on Firefox's reputation. But that's not what's happening: it's a bug that manifests in what probably looks to the user like a simple way, but tracking down the problem and fixing it is not simple at all. People are working on it, and it looks like it'll be fixed in a public release before too long.

Agree: this is the process working.