Only about 35% of users are aligned with what Moonchild wants for Pale Moon. About 40% just want old Firefox with XUL addon support, and another 20% basically wants LibreWolf. Only now it has become evident that what Moonchild wants Pale Moon to be isn’t what most users want in a browser. One can VaakĪs this post has shown (with more details in the original forum post) Moonchild has clearly known what he’s wanted the browser to be for years. But who knows? Maybe one day Google will take things one step too far while Mozilla gives up and falls in line, forcing a larger united front to form behind Pale Moon. In an ideal world people would work together with a united goal and make compromises where necessary, but sadly we’re not in that timeline. It’s a fundamental difference in philosophy.Īs it stands, Pale Moon continues to hold the bastion as the last true “third option” in a web that is all but Blink and did address the matter of collaboration in the main post. By now most of the tech-inclined are already aware of how Manifest V3 will break core functionality in uBlock Origin but does anyone believe that’s the worse that could happen? Google is always moving in a direction that enables more control over the user and how the user interacts with the web, whereas XUL is the freedom to do whatever.
#Pale moon vs firefox mod#
Naturally multiple tab rows is an “unsupported” mod to Firefox so obviously Mozilla will not care to fix it. The CSS hacks that used to allow you to do this in Firefox Proton are getting jankier with new releases and likely one day will stop working altogether.
For example, I consider multiple tab rows to be essential for a power user browser and XUL addons allow you to do this easily. I think it’s great that there is at least one regularly maintained browser that allows you to do basically anything you’d want to do within a browser. The whole reason Pale Moon continues to exist is because of XUL and the near limitless potential it has. Maintenance requirements for XUL addons (on Pale Moon) are far lower than for WebExtensions on Firefox because there’s no underlying entity (Mozilla) that insists on making compatibility-breaking changes just for the sake of change whenever they feel they need a “fresh” look (first Australis and now Proton). The decision has not been made in this regard yet. We are aware that without further outside help, this will still take considerable time and web compatibility will remain less than desired/optimal while we work on improving the adherence to current trends in web "design" (mind the quotes).īasilisk browser may be discontinued as a consequence, or it may be split off. With less pressure on us to mould and feed the extension ecosystem, we will continue our efforts to work on implementing the major blockers that have caused increasing web compatibility issues (primarily issues in JavaScript, Google frameworks, Google WebComponents, and a few persistent yet difficult to implement specs. These changes will take time but should improve compatibility significantly. With these two in place, the development team can focus on improving the web browser's compatibility and tackle major compatibility issues.
0 kommentar(er)
