Re:Firefox 73
by sefrost on Tuesday February 11, 2020 @11:37AM
(#22299794)
This happens to me a lot in the Chrome developer tools as well. Especially with hot reloading, so would love any advice to help with it. Chrome is the only application I ever have to force quit.
[ Parent
| on HN ]
Re:Firefox 73
by dmitryminkovsky on Tuesday February 11, 2020 @11:49AM
(#22299906)
Happens to me in Chrome too, specifically when I reload a page that's stopped at a breakpoint. Instead of force quitting the whole application, check out Window -> Task manager. There you can force quit just a single, specific tab without closing the whole application.
Re:Firefox 73
by neetodavid on Tuesday February 11, 2020 @01:53PM
(#22301380)
The chrome task manager (hotkey Shift+Esc) is good for killing tabs
For large pages where source changes cause problems I will sometimes put logic inside conditional breakpoints. It's not great for huge changes (though you technically can put a lot of code in there) but for small things like quickly sanitizing null inputs it works fine.