3 ms·

If a tab crashed I would be sympathetic to this point of view, but the entire browser is killed. So no, it's not google's fault in my book. As for testing. Rea

If a tab crashed I would be sympathetic to this point of view, but the entire browser is killed. So no, it's not google's fault in my book. As for testing. Really, you expect them to test against Linux Kernel 4? If so, how about 2 as well? Just in case you didn't realise. Kernel 4.20 (the one that changes this behaviour so it wouldn't show the Firefox bug) was released in December 2018. That's 4.5 years ago.

rvz 3y ago
Exactly. That's even worse since the entire browser is crashing. Its not Google's fault if Firefox was unable to prevent a crash or display the page when Safari, Chrome, etc can load and run it without crashing. Once the user sees this crash constantly, switches to Chrome and it doesn't crash, then they blame the crashing browser which is Firefox. Rightly so. Really says a lot about these Firefox developers and users immediately blaming Google for their JS code when Firefox was supposed to protect or handle against cases like this without crashing.
- db48x 3y ago
  Mozilla isn’t blaming Google here, or they wouldn’t have bothered to fix the bug. When you drill down to the root cause of something, you have to carefully note down all the proximate causes that you found along the way, otherwise you won’t have a complete understanding of the problem. In particular, noticing that Google’s machine–generated javascript is doing something allowed but out of the ordinary is important for explaining why you only just now found out about this bug in code that has been working just fine for years.