News for hackers. Stuff that matters.
Re:Firefox’s New WebSocket Inspector by jjoonathan on Tuesday October 15, 2019 @05:15PM (#21263882)
I seem to be running across an increasing number of buttons that simply don't register clicks in Firefox. It's probably not FF's fault -- my money would be on webdevs leaning on chrome-only features -- but it does bring my Firefox session to a screeching halt and sends me back to chrome, usually after filling a form and trying to hit submit. It happens about once a week.

That's probably way too vague to be helpful unless someone else knows what I'm talking about, but if nobody does, I suppose knowing that could help motivate me to isolate and reproduce the issue next time it happens.

Re:Firefox’s New WebSocket Inspector by cmroanirgo on Tuesday October 15, 2019 @06:38PM (#21264775)
A lot of the time that it happens to me, and I've bothered to check, it's always been some react code that's had errors.
Re:Firefox’s New WebSocket Inspector by baroffoos on Wednesday October 16, 2019 @12:11AM (#21266970)
Strangely my routers web admin will not load at all on firefox. Checking the console shows there is a js error about an undefined variable. Really wonder how they managed to stuff up the page that bad.
Re:Firefox’s New WebSocket Inspector by cfreeman on Tuesday October 15, 2019 @08:26PM (#21265705)
It could be the different extensions you have installed. Often this happens with adblockers, so if you use incognito mode or another browser it would fix it.