2 ms·
Back when I still had to support bleeding-edge web apps more than a few of my bug reports were from Pale Moon users because the devs couldn't configure their co
by kevingadd 7y ago
Back when I still had to support bleeding-edge web apps more than a few of my bug reports were from Pale Moon users because the devs couldn't configure their compiler properly and were always behind on bug fixes. Impossible to act on that stuff, though I tried. Once I realized how bad PM's security story was I gave up on supporting it, not gonna expose my development machines to that.
- smnthermes 7y ago> Once I realized how bad PM's security story was I gave up on supporting it, not gonna expose my development machines to that. Fake news. Firefox had sandboxing (that was the excuse for deprecating XUL/XPCOM) before Chrom* and Electrolysis: 1. https://developer.mozilla.org/en-US/docs/Archive/Add-ons/Security_best_practices_in_extensions https://developer.mozilla.org/en-US/docs/Archive/Add-ons/Sec... 2. https://developer.mozilla.org/en-US/docs/Archive/Add-ons/Displaying_web_content_in_an_extension_without_security_issues https://developer.mozilla.org/en-US/docs/Archive/Add-ons/Dis... 3. https://developer.mozilla.org/en-US/docs/Archive/Add-ons/Interaction_between_privileged_and_non-privileged_pages https://developer.mozilla.org/en-US/docs/Archive/Add-ons/Int...
- lima 7y agoFirefox did not have process-level sandboxing till Quantum. Exploit a JS bug in the renderer and you had code execution on the host OS. "Fake news" accusations aren't welcome on HN, people here prefer to disagree amicably.