AstroSkipper

Thanks for reporting! TBH, I didn't expect any further root certificate updates via CAupdater 1.0 or Certificate Updater 1.6. Great news!

At the moment, I have reverted to the last officially compatible version 1.46. But I will test the 1.56 version again. Thanks for the hint! @feodor2 I moved to the most recent, final version of uBlock Origin which is 1.62 at the moment. The logger works fine in multi-process mode but in single-process mode, the logger popup window is very unstable. Some extensions, scripts and whatever else interfere considerably with the loading and display of the logger popup. It often remains empty. Resizing the logger window helps in some cases. I investigated this further and found that changing the advanced setting loggerPopupType from popup to normal may be a solution. In this case, the logger is opened in a normal window in which it loads fine as far as I could see until now. At least, on my computer with its current configuration. I'll keep an eye on that. P.S.: @feodor2 Now, I have realised what you meant by using the context menu. I have never opened the logger interface via its icon context menu before. Indeed, this also works in both process modes to properly open the logger in a tab or window. However, changing the advanced setting loggerPopupType from popup to normal is of interest for those who prefer only one normal left-click on the logger icon as usual.

Today, I created a subroutine to catch errors ,for example a TypeError, caused by the document.getElementById() or document.querySelector() commands when a page is loading too slowly. I use these error messages to check as long as a successful access to an element is granted and then to immediately execute the desired commands. This avoids unnecessary, static setTimeout commands and error messages in the Browser Console.. Works like a charm. And I'm not in the mood to use observers everywhere.

I already wrote about this general.config.sandbox_enabled preference in terms of the Nuchi-Sporif script loading method and other ones:

I thought the general.config.sandbox_enabled preference is the one to be enabled if the user wants to use the sandbox feature.

At the moment, I have reverted to the last officially compatible version 1.46. But I will test the 1.56 version again. Thanks for the hint! @feodor2 I moved to the most recent, final version of uBlock Origin which is 1.62 at the moment. The logger works fine in multi-process mode but in single-process mode, the logger popup window is very unstable. Some extensions, scripts and whatever else interfere considerably with the loading and display of the logger popup. It often remains empty. Resizing the logger window helps in some cases. I investigated this further and found that changing the advanced setting loggerPopupType from popup to normal may be a solution. In this case, the logger is opened in a normal window in which it loads fine as far as I could see until now. At least, on my computer with its current configuration. I'll keep an eye on that.

Keeping single-process mode is really a good idea and very important for those running Windows XP on old, weak computers. Actually, this mode works much better in Mypal 68.14.7b than in the previous releases. I've already mentally and emotionally prepared myself for the next compatibility breakages you'll soon be unleashing. I am really curious to see what will no longer work in the next version as it did in Mypal 68.14.5b. In the meantime, I have written a whole series of UC.JS scripts to be on the safe side if a lot of my older stuff do not work anymore. Hope the Custom Buttons extension will still work in your next Mypal 68 release as it should actually be able to run in newer Firefox versions up to at least 136 as well. And if it works there, it should also be possible in newer Mypal 68 versions with a much lower JavaScript level.

@feodor2 When creating UC.JS scripts, I noticed that some Vanilla JavaScript commands behave differently in single-process mode compared to multi-process mode. When starting the browser, loading new tabs or windows, accessing elements via document.getElementById() and especially via document.querySelector() needs much more time in multi-process mode than in single-process mode. Is there any explanation for this? Is this by default or rather a Mypal 68 specific behaviour? When, for example, starting the browser with the about:addons page, it takes nearly 8 seconds after DOM is loaded to be able to access an element in multi-process mode via document.querySelector() . In single-process mode, it can be accessed directly. This is very strange and does not make the multi-process mode particularly attractive.

Where did you see that this switch is only for automatic definitions updates? BTW, I have not only linked a screenshot, but also quoted from the online help: That sounds to me not only like definition updates, but also like programme updates. I cannot judge what is ultimately meant by this, as I do not have a licence.

IMHO, a very simple and clean way is to unpack the new Mypal 68 archive file to a new folder, open the browser from there and create a new profile with the same name of your old profile to be imported by using Mypal 68's profile manager. Then, close the browser. Now, delete all files of your just created profile folder and copy the old ones from your backup into it. Now, start the browser again with this new profile. Done! At the moment, I have 10 different Mypal 68 programme folders and many, many profiles, only for the purpose of developing and testing, of course. No problems here.

TBH, updating New Moon 28 is as quick and easy as reverting to a previous version. So, there is really no reason to be afraid.

Thanks for your report! Avast 18.8.4084 was a terrible version from the start. As I reported at the time, it produced many problems. In the end, it couldn't even be uninstalled in the normal way. When I have the time and inclination, I'll try Avast 18.5.2342, although I've actually shelved Avast.

I have looked at the documentation for disabling programme updates. Supposedly, there is an option with the entry: Did you really try this switch?

Interestingly, your French Amazon site runs better in New Moon 28 than in Mypal 68, i.e. switching between the different models works, albeit rather sluggishly, at least on my old computer.

I'm really sorry, but I'm not a fan of meaningless drivel. You should use your time more wisely!

Nobody asked you to neglect your "career". BTW, no one has spoken of this, and it is not the issue here at all. But if you take the trouble to reproduce something I said, then it should correspond to what I said. And if you don't really understand it, you should either quote it verbatim as you have done now: Bingo! or simply not refer to it at all. P.S.: I think bragging about your "above-average salary", whatever that means and whoever cares, is rather inappropriate and doesn't belong here.

I think it is more something like that ... There was no alpha but a correlation coefficient r of r > 0.95 to express the almost perfectly linear correlation between two statistical variables, the user interest and the (actually my) willingness for publishing. If you want to refer to what I have stated, then please in a correct way. To put it in simple, non-mathematical terms, the greater the user interest, the greater my mood to publish something.

I already reported here that Amazon Germany stopped working properly in Mypal 68.14.x: https://msfn.org/board/topic/183495-mypal-68/page/76/#findComment-1275586 Your posted article on Amazon France has even led to a crash of Mypal 68.14.7b on my old Windows XP machine when clicking on 8 ports Métal 34,99€. The causer of this misery is of course not @feodor2, but the website designers at Amazon, strictly following the rule: The more bloated, the better. However, I personally hope that @feodor2 can fix it one day.

Not necessary - here the custumbutton already published by you /*Initialization Code*/ var prefName = "security.csp.enable"; var enabledImage = "data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAUCAYAAACNiR0NAAAAAXNSR0IArs4c6QAAAARnQU1BAACxjwv8YQUAAAAgY0hSTQAAeiYAAICEAAD6AAAAgOgAAHUwAADqYAAAOpgAABdwnLpRPAAAAO1JREFUOE9jZPgPhFQFIAOpCalqGNi31HQdfQz8R6Gb4drVwLGNwGlQGWQxWAC5Iqnjg7LnwtSD/G0GFYSFpzSQzwTEfWjiIANhPgCx7aGG6COpg6bD/wxuWLzagWYgcgSCDDSG6pmHzcBuHGEH83IEmjxI3A4qpoDNQJBrcMFcpDCDqYFZFACV248chiBJayzGgcLrA5I4SF0tTCOQNsCiByxkBLXlJVTBOSCdA8RiaGEIMnADkoGmuAwEGSqO5C2QxlYgPg8VY4bSoCQCgqFIasPQDMViB2ZI/iFKFUQfCUqJy/WjBhIXTnhUAQCxF7FzNVSQlgAAAABJRU5ErkJggg=="; var disabledImage = "data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAUCAYAAACNiR0NAAAAAXNSR0IArs4c6QAAAARnQU1BAACxjwv8YQUAAAAgY0hSTQAAeiYAAICEAAD6AAAAgOgAAHUwAADqYAAAOpgAABdwnLpRPAAAAOlJREFUOE9j/M/AAERUBCADqYlBzhvpBv6jMAjgYagGiW04ToMajCwGYoPC3BVJHR+UPRemHqTADCoIiyBpIJ8JiPvQxEEGwnwAYttDDdFHUgd2IUjSDYtXO9AMRE4RID3GUD3zsBnYjSPsYF6OQJMHidtBxRSwGQhyDa40mYsUZjA1MIsCoHL7kcMQJGmNxUBQeH1AEgepq4VpBNIGWPSAw9AIastLqIJzQDoHiMXQwhBk4AYkA01xGQgyVBzJWyCNrUB8HirGDKVBSQSkNhRJbRiaoUTl5T94whc93IkykJQCZNRAygtbAOb2sXODGkDmAAAAAElFTkSuQmCC"; this.onclick = function (aE) { if (aE.button === 0) { Services.prefs.setBoolPref(prefName, !Services.prefs.getBoolPref(prefName)); setSelfImage(); } }; function setSelfImage() { if (Services.prefs.getBoolPref(prefName)) self.image = enabledImage; else self.image = disabledImage; } setSelfImage(); replace "security.csp.enable" with the desired thing Toggle CSP is a custom button I created for only toggling one preference in about:config and made it available almost two and a half years ago. To be honest, there wasn't much interest in this button. And your suggestion to use this button as a template is a little off the mark. Toggling the browser.tabs.remote.autostart preference has no direct effect while the browser is running and can't be a solution as you actually should know. More steps are to perform. If you compare the two buttons, you should notice that the PMT - Process Mode Toggler custom button has a much more complex functionality than the Toggle CSP custom button. BTW, I have revised the Toggle CSP custom button some time ago and designed it so that the manual switching of the security.csp.enable preference, for example, in about:config is also registered by the custom button to always display the correct status via the button image as well as via the button tooltip, even in such or similar cases. However, the PMT - Process Mode Toggler custom button does not need such modification, and thus, I have already removed it again, as solely toggling the browser.tabs.remote.autostart preference has no effect on the current browser session in terms of its process mode. Why to tease then? Teasing? I do not tease anyone. I just demonstrated what custom buttons are capable of, and I made it clear to think about publishing if sufficient interest was shown. No more, no less. However, I cannot see this at the moment. And to be honest, I don't know what your problem actually is. Regarding the PMT - Process Mode Toggler custom button, which I already made available for you only, I am the creator and decide for myself if and when I publish something. Just like you do when it comes to Mypal 68. One thing is clear: you are you, and I am me. No pills will help. @feodor2 If you want to tell me something specific, you should articulate it as clearly as possible. I’m not a fan of reading between the lines or subliminal hints.

Thanks for the hint! Since the version 5.2, I have been using the portable version exclusively. The installer version stopped working as you also noticed. I have now installed DiskGenius 5.6.1.1580 under Windows XP. However, on my old computer, this version needs much longer for starting as the previous versions. I am not sure if it is really fully compatible. I have to observe this version over a longer time.

@feodor2 Here is my feedback to your new release Mypal 68.14.7b: I can confirm that the loading and scrolling websites issue in multi-process mode doesn't occur anymore. Same applies to the issue that the GIF image animation was broken in single-process mode. This issue doesn't occur anymore, either. And last not least, same applies to the issue that the last confirmation popup is incorrectly displayed when installing extensions. This issue doesn't occur anymore, either. Good job! So, thank you very much for your quick bug fix version and for all your efforts! Greetings from Germany, AstroSkipper

Then you simply haven't read many of the posts in this thread and in my thread about UXP browsers. FYI, I have neither ruled out nor promised a release of the PMT - Process Mode Toggler custom button even though I generally create custom buttons for personal use. I have written at least six new custom buttons for Mypal 68 in the last few months. And long before that quite a few for the UXP browsers. After releasing some of them, I could not recognise any significant interest. BTW, I have also deepened my JavaScript and CSS knowledge considerably to modify already existing UC.JS scripts and especially to create new ones from scratch. Both are in full swing. It should be mentioned at this point that everything is purely self-taught. Programming is just a hobby of mine. I never learned it professionally. Anyway! Due to a lack of real interest in legacy custom buttons, it seems pointless to me to publish my custom buttons at the moment. I have put it in a nutshell here: Apart from that, I have already published so many different things in this forum that it is difficult for me to keep track. But I don't necessarily have to publish things that nearly nobody appreciates or wants to use. That's exactly how I see it. But we are probably the exceptions here. And then the user would also have to familiarise themselves with the special JavaScript language and its syntax provided by the Custom Buttons extension (there are commands and variables that do not exist in the standard JavaScript language) ... After all, a similar button as a template for a desired one is not always available. Long story short: the ball is now in the court of the readers of this thread.

Just a small hint. My custom button is called PMT - Process Mode Toggler. It toggles the process mode and is therefore a toggler. Back to your statement. If you really want to install the Custom Buttons extension for only one custom button without any deeper interest in Mypal 68 anyway, since you are a user who always deletes everything after a short time, then it's not worth the effort at all. This extension actually only makes sense if you want to retrofit missing features or if you plan to replace a lot of extensions by custom buttons which have only a very low resource consumption and are much less restricted than webextensions. These custom buttons can do things which webextensions are not allowed to do . And especially my self-created custom buttons do exactly what I want them to do.

To get something installed doesn't really mean anything. What matters is whether it works properly in all its features. And actually as always, a superficial view is not purposeful. That means a thorough examination is necessary.

@NotHereToPlayGames BTW, such a legacy Custom Buttons extension I have already provided in September of 2022 in my thread "Extensions and custom buttons for UXP browsers - Corrections, modifications, adjustments, and special recommendations" which can be found here: Custom Buttons - The extension for installing custom buttons. As already said, this version cannot be installed in Mypal 68. And here are more of those old Custom Buttons extensions you are referring to which are all incompatible with Mypal 68: https://sourceforge.net/projects/custombuttons/files/ Can be checked very easily. The good is you won't "have to dig through stacks and stacks and stacks of DVD-Rs" to find your Custom Buttons extension because with a probability bordering on certainty, those old versions, if you ever find any, won't either work in Mypal 68.