stnvh

I've always wondered why Firefox don't grab hold of the "renegade" space they already occupy, with confidence through their existing users, an alternative and genuinely independent browser down to the engine. They are the market leaders of non-webkit, a huge strength among chromium copycat popup shops with identical wins and failures... or do I have to write the TV ad as well?

I feel confident to assume the majority of dedicated Firefox users will read and think of this feature release, et al most new features as of late, as trivial. The true benefit of using Firefox in itself isn't "ease of planning camping trips" but something much more.

Reassuring to hear I'm not the only one, and would consider this a normal use case for the browser, in fact one of the main reasons I use Firefox over chrome as it's simpler to manage than the latter.

I was hinting in my original comment if these cases are contributing to crash reports in any capacity there is a small chance they could be misattributed towards the claims in the post, especially if memory is not freed correctly on shutdown. Even more so if any memory allocation is shared between processes / helpers.

If I quit normally, don't wait for the "timeout" and force quit I still get the crash report UI immediately which suggests to me something funky going on.

10% is a crazy high percentage to claim for bitflips.

Long hangs / never closes, crash report screen triggers often. macOS. This occurs for me when launching instances from the about:profiles page and using each instance for what I'd describe as normal use

Try running two instances of Firefox in parallel with different profiles, then do a normal quit / close operation on one after any use. Demons exist here.

The waterfalls match the ones generated by WebPageTest, though they could be using a third party tool themselves

Indeed. "Our server got hacked" sounds awfully more dramatic in a self-proclaimed crisis, laying the ambiguous notion of responsibility toward the "service" while maintaining the guise of ownership. Hey ho.

Interesting on stripe's response to this matter. 'Debug environment spew leads to unauthorised api usage' - unfortunate and well worn. Like a good pair of slacks, it was simply your turn to wear them this time

It seems more like the devs at MS know their code works on Firefox but have been asked by exec to push chromium(-esque) because edge is now webkit.

sidenote: this is a multi-billion $ company, no excuse to ignore any platform with their capacity, front face it looks like they can't build a good app anymore, especially if it works anyway with a simple string change in the browser - heck, web devs had to factor in ie7-8 polyfills built by the community only a few years ago. no excuse.

Using Firefox with the user agent changed to chrome seems to get around this

classic emoticons aren't translated though ;)