The Pale Moon Gecko fork was developed somewhat independently with parts of Gecko being back-ported to Pale Moon. Mozilla Firefox was using a rendering engine called Gecko at the time. Pale Moon begun as a fork of Mozilla Firefox in 2009. A bit of history is required to understand why that is a huge undertaking. The only viable solution, for end-users, would be "the complete implementation of Google WebComponents" as MoonChild put it. Switching to some other web browser seems like the more efficient choice if something doesn't work in Pale Moon. The one French-person using it would have to waste an afternoon writing one. Nobody is going to write some special extension to make some localized news website in France work correctly.
#Pale moon reviews 2017 install#
What are Pale Moon users supposed to do, install a special extension for Facebook, Instagram, Twitter, GitHub, Hacker News, Reddit, BitChute, YouTube and dozens of other websites? Nobody would do that even if such extensions were available, and the reality is that they won't be. Installing a per-site extension for every larger website using modern web features is not a workable solution.
#Pale moon reviews 2017 code#
Stephen, a Pale Moon user involved in a project with code on GitHub, complained to GitHub about the latest changes to their website. Microsoft GitHub Doesn't Care About "Unsupported" Web Browsers That's exactly what happened to a few Pale Moon users a few days ago. It's not if you are trying to merge code to a repository on GitHub and it doesn't work because GitHub changed the site and the new version uses WebComponent elements Pale Moon does not support. The missing buttons in the example above may seem like a trivial problem and it is in that example. Notice how Chromium-based NAVER whale has expand all and collapse all buttons while Pale Moon doesn't. WebComponents in NAVER whale and Pale Moon. Consider this screenshot of a "Web Components Demo" made by the Michigan State University Plant Research Laboratory in NAVER whale and Pale Moon: Some custom elements work fine, others do not. Pale Moon does support WebComponents but only to a certain degree. The reason? Moonchild doesn't like that GitHub is increasingly relying on web standards the Pale Moon web browser doesn't support. The developer of the Pale Moon web browser announced that Pale Moon's source code is being migrated off Microsoft GitHub yesterday. Notice how it's showing a cookie warning, and a lot of big-tech sites, in new tabs. It is increasingly falling behind the bigger browsers and more and more websites are broken in it as web developers deploy web standards other browsers, but not Pale Moon, support. There also Pale Moon with it's own Goanna rendering engine. There's a ton of web browsers based on Google's Chromium code-base, a few mostly iOS and macOS browsers based on Apple's Webkit engine and then there's Firefox with it's own Quantum rendering engine. There's plenty of web browsers to choose from on desktop computers but there's not much of a choice if you look beneath the surface.