![]() ![]() As you will notice in the release notes that very few of the security bugs listed actually made it into the ESR train. Even then we backported some security related bugs not deemed critical enough during that time as well. This is how it has always worked, we just had an easy time by riding that ESR24 train for a while. We are actively always tracking security bugs and applying all those that are applicable to our codebase. Please again remember we are on top of this and resolutions will come.Ī previous comment mentioned their concern about security issues with our further splitting from Firefox. There is a link on that page as well to a forum thread to report ones you have that aren’t working properly. Please, check to see which of the reported add-ons is known to have issues with Pale Moon 25. Our efforts require your assistance and your understanding. Also, consider we can not have known for sure out of the ~15 thousand add-ons currently up on AMO which ones would effectively break until we had broken them. With some time and effort things will normalize. You have to understand that this was a necessary step. Due to the very poor responses back from add-on developers regarding direct and specific Pale Moon support I have been scrambling to deal with these breakages. I am working very hard to create these pseudo-static add-ons (like I did last night for ABP). Greetings, Me again, Your friendly Pale Moon Add-ons site administrator and your one last hope for Pale Moon on XP! #QUPZILLA ENDED XP SUPPORT INSTALL#So the long answer is that while everyone can install Classic Theme Restorer, it won’t necessarily fix the problems that are causing people to migrate to other browsers. My friend is sticking it out and hoping that Mozilla and its extension developers will eventually iron out the bugs. I switched to using Pale Moon as my default browser and am sporadically building a “fresh” Firefox profile when I have nothing better to do, which is almost never. We both have extensive profiles and are not enthusiastic about rebuilding them from scratch in the hope that this will fix Firefox’s and Classic Theme Restorer’s problems (as Classic Theme Restorer once suggested it might). Installing the Classic Theme Restorer extension made it buggier and less stable still. Long answer: On a friend’s machines (one Win7圆4 and one Win7x86) and on my own machine (Win7X64), updating from pre-Australis to post-Australis Firefox resulted in Firefox being markedly buggier and markedly less stable. Short answer: Everyone can install Classic Theme Restorer! ![]() Mozilla Corporation service tools are not build anymore.The WebAPP runtime is not build anymore.The browser's Global Unique Identifier has changed, and extensions with Pale Moon's or Firefox's GUID can be installed natively now.This was done by disconnecting Firefox's compatibility mode by default. Pale Moon will retain Firefox compatibility with Firefox 24.x extensions regardless of the browser's own version.There is however an option to override the user agent on a per-site basis so that this should not be much of an issue after all. Users may experience issues on some sites because of that. This means that Pale Moon won't use a Firefox indicator in its UserAgent string anymore. Firefox Compatibility mode is disabled by default.Several compatibility changes have found their way into Pale Moon 25 as well: You can check add-ons however in the sync settings so that they are synchronized across devices. #QUPZILLA ENDED XP SUPPORT FREE#The author notes that the old sync server will be disabled in a short period of time after the release of Pale Moon 25 to free up infrastructure and reduce costs.Īnother sync related change is that add-ons are not synced anymore by default. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |