Re:Please consider not adopting Google WebComponents
by zamalek on Tuesday March 17, 2020 @11:59AM
(#22606201)
They have blown things out of proportion (see parent comment). Only extremely minor browsers will be affected. Chromium (Chrome, Edge, Opera), Quantum (FF) will be fine. I suspect even the likes of KHTML will add support for it.
Pale Moon is a fork of Firefox made before the removal of XUL (as I believe is their selling point). They would have to back-port Web Components (which may be impossible due to Quantum) or write it from scratch. This is all really hard for them because they likely have fewer than 10 active developers.
Re:Please consider not adopting Google WebComponents
by Udik on Tuesday March 17, 2020 @12:08PM
(#22606327)
Can't they just ship the browser with js webcomponents polyfills?
Re:Please consider not adopting Google WebComponents
by kevingadd on Tuesday March 17, 2020 @04:06PM
(#22609685)
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.
[dead]
Re:Please consider not adopting Google WebComponents
by lima on Tuesday March 17, 2020 @05:09PM
(#22610457)
Firefox 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.
Not alone that, they are rude and shit into the face of a big part of the Linux community with threatening them in the worst way possible.
Then we had a server hack with compromised binary files....
People should be made aware of Pale Moon and their amateurish activity, so they can immediately uninstall this danger-ware from their systems!