AstroSkipper

@feodor2 I don't know if you have read my post quoted above. The logger in the most recent version of uBO 1.61.2 has now completely stopped working in Mypal 68.14.4b and 68.14.5b. Neither when running single-process mode or multi-process mode. I therefore reverted to the last officially compatible version 1.46, as uBO is unfortunately useless without a functioning logger.

I can't say what's going wrong in your system as I never have used Windows 2008. And I don't know whether New Moon 28 targets this OS at all. Under Windows XP, the "Make New Moon the default browser" button has always worked like a charm. And if this feature didn't work in other browsers, I either edited the respective registry entries manually or I used the tool Default Browser 1.8. Unfortunately, this tool is for Windows XP only but maybe, there is also a tool which does this job under your OS. Here are important registry locations which were set by me for using New Moon 28 as default browser under Windows XP: HKEY_CLASSES_ROOT\Applications\palemoon.exe HKEY_CLASSES_ROOT\http HKEY_CLASSES_ROOT\https HKEY_CLASSES_ROOT\ftp HKEY_CLASSES_ROOT\PaleMoonHTML HKEY_CLASSES_ROOT\PaleMoonURL HKEY_CURRENT_USER\Software\Classes\Applications\palemoon.exe HKEY_CURRENT_USER\Software\Classes\http HKEY_CURRENT_USER\Software\Classes\https HKEY_CURRENT_USER\Software\Classes\ftp HKEY_CURRENT_USER\Software\Classes\PaleMoonHTML HKEY_CURRENT_USER\Software\Classes\PaleMoonURL HKEY_LOCAL_MACHINE\SOFTWARE\Clients\StartMenuInternet\Pale Moon web browser HKEY_LOCAL_MACHINE\SOFTWARE\Clients\StartMenuInternet\PALEMOON.EXE Under the registry path HKEY_LOCAL_MACHINE\SOFTWARE\Clients\StartMenuInternet all registered standard web browsers are listed. So if you want to be offered a standard browser, you have to enter the corresponding one there. BTW, New Moon's native function for setting it as default browser is SetDefaultBrowser(). When checking its source code, you will exactly know what actions the "Make New Moon the default browser" button performs.

@feodor2 Unfortunately, I have to report that the website amazon.de is no longer working in Mypal 68 as before. I tested it in both versions 68.14.4b and 68.14.5b. Here is one link as an example: https://www.amazon.de/Original-Blumax-DMW-BCG10E-Panasonic-DMC-TZ31/dp/B00I04P3ZU?nsdOptOutParam=true&sr=8-3 When I try to open this page, the loading process is a torture compared to how it was months ago. It always stays at 100% CPU utilisation regardless of whether the website has been fully loaded (or appears to be fully loaded) or not. Although my hardware is weak (single core CPU Pentium 4 Northwood 2.8 GHz), amazon.de has worked tolerably well in Mypal 68 in the past. BTW, in New Moon 28, this site is loading much faster and comes to an end without 100% CPU utilisation. As far as I noticed, the issue is related to the loading of images and media. Even the additional use of uBlock Origin couldn't help, unless you neuter the site to the point of informationlessness. P.S.: With the help of additional user scripts and own filters for uBO, I was able to tame a bit the amazon.de website. Now, the loading process finally ends at some point. But all loaded images and media definitely lead to extremely higher processor utilisation than before. The entire loading process still takes some minutes.

Edited 2 hours ago by seven4ever But @feodor2 didn't say that. It is just your request. Your post is a bit misleading due to your wrong quotation. Anyway! You can vote for a new SSE version here: https://github.com/Feodor2/Mypal68/issues/164

Thanks for your opinion! Then, I will update the download links as soon as possible.

As @feodor2 already tested this extension in Mypal 68, I think it costs only seconds to test it in a more recent Firefox version. I assume that a developer also has access to more modern Windows versions. But if you want to test this extension, do it and report here your results. I'm not going to do that because I don't care about modern browsers. I definitely don't develop anything for these browsers.

Last time, you stated that you do not surf anymore under Windows XP. You have to stand by your statements at some point. You've given up Windows XP and you've said so everywhere. You only need Windows XP for your oldtimers, but not for everyday surfing. Somehow, you're just a flag in the wind. Like this today and like this tomorrow.

And please, speak only for yourself! You don't know what others think or want. This is a very bad habit. And since you don't actually have any use for this browser, it's not particularly relevant what you would like to see in the development of this browser. Sorry, but that is the truth. But if you want to keep shooting at me, then don't force yourself. But, as is often the case with you, it has absolutely nothing to do with the real issue.

Why should I test things I hate and which are already reported elsewhere to be working? So, there is no contradiction at all and nothing is misleading. This thread is not about modern Firefox browsers. So, I fear you are somehow confused and misled as you didn't really follow this thread and my thread about Mypal 68 in its entirety. And BTW, you did nothing meaningful here. One doesn't have to put his two cents in everywhere. Especially if one doesn't need Mypal 68 at all. And as you already stated, you are a Windows 10 user at home. This browser is not meant to be used under this OS. And you do not surf anymore under Windows XP. So, you have no real use for this browser.

As far as I know and have read about this extension, it should work in more or most recent Firefox versions. However, since I hate all recent releases of Firefox and am a die-hard Windows XP user, I did not explicitly test the most recent Custom Buttons extension in more recent Firefox releases. I use the newer, crappy browsers as they are and only when I have to. I know. You are the creator of Mypal 68, and you have to decide what will be changed and updated in your browser. I am just a creator of custom buttons, CSS styles and scripts, a code modifier who tries to fix already existing code to make it working again. Nevertheless, I developed a lot even for Mypal 68. Anyway! Do what you have to do but please keep in mind that compatibility is a valuable asset contrary to what Mozilla is doing . To preserve the possibility to run some older stuff in more recent versions of Mypal 68 would be great, though. But if it is not possible to preserve certain, old stuff due to important and necessary changes, then, for better or worse, that's what will happen. Don't worry about my beloved custom buttons! I have already started to port my custom buttons into UC.JS scripts. Unfortunately, I have to change a lot, and the JavaScript syntax is different, but I have steadily expanded my JavaScript and CSS skills. But one thing is crystal clear. The Custom Buttons extension is simply great, incomparable and in all its facets irreplaceable. So, try to keep the compatibility with the Custom Buttons extension as long as possible! BTW, I have already fixed all issues by myself in Mypal 68.14.5b regarding the broken UC.JS scripts and CSS styles. Except the Custom Buttons extension, of course. For the UserCSSLoader, I created a complete, new CSS stylesheet. But it was much more complicated to do as before which means I don't like the new CSS. The old one was much easier and more effective. I don't understand why the more recent has to be the more complicated and restricted in these days. And I replaced the Extension Options Menu script by a more recent one. Unfortunately, I could no longer save my version.uc.js script, and therefore I had to replace it with something similar.

I don't think that 99% users won't bother with "editor path" and consider it as broken. The popup clearly tells the user to set a path to their favoured editor via a preference called view_source.editor.path in about:config for editing CSS files by this script. As it is totally self-explanatory, I have not mentioned this. If a path to your favoured file manager was set in line 46 of this script and a path to your favoured editor via view_source.editor.path, then all menu items will definitely work. And you doesn't seem to have understood what the "Import styles" entry is intended for. When clicking this entry, then all CSS styles will be loaded again on the fly. In the case that all styles have already been loaded, then clicking onto it will logically do nothing. But you can check very easily whether this feature is working or not. Copy a new style in the form of a CSS file into the CSS folder while the browser is running. It is not yet loaded. Now click on "Import styles", and the stylesheet is loaded immediately, i.e. without restarting the browser.

Great! Mypal 68.14.6a again with browser.xul. But who or what is xioxui? Maybe, you meant xiaoxiaoflood? Anyway! Development must go on but keeping compatibility as far as possible would be really great. That's why I don't like Mozilla's way of development. New releases, and compatibility breaks without end.

I'm glad to hear it. 1. What search are you talking about? 2. Sorry but that is not true. The UserCSSLoader script is fully working in Mypal 68.14.4b. Here is a short demo: The "Import styles"is only necessary if new styles are added or some styles have been edited. When starting the browser, all styles are automatically loaded by this script. And what do you want to open? The CSS folder? A stylesheet in an editor? The userchrome.css file? Please describe it a bit more detailed! I can't do anything with statements like that. In any case, if all is configured as I described in my instructions very detailed inside the uploaded archive, then all features of the UserCSSLoader script are definitely working. The reported issue was its CSS stylesheet which does not work in Mypal 68.14.5b only. 3. Sorry but that is not true, either. The Custom Buttons extension works fine in Mypal 68.14.4b. At the moment, I have installed 11 custom buttons in this browser. Here is a short demo: For installing a custom button, you click the "Open file" dialogue from the browser main menu, go to the Restart & Purge v2.0 10-12-24 003806.htm file I uploaded for you and click onto it. Everything else goes without saying. If you want to see my most recent Process Mode Toggler custom button in action in Mypal 68.14.4b, then have a look at here: https://msfn.org/board/topic/183495-mypal-68/?do=findComment&comment=1275154

Here is a short demo of the Extension Options Menu script: This script is no longer working in Mypal 68.14.5b due to the recent changes. You won't find anything comparable. This is an Add-ons Manager in the form of a toolbar button. Webextensions can't do that due to their restrictions. That's why you can't find any working Add-ons Manager extensions on Mozilla Firefox extensions page. P.S.: At this point, I should mention that this script works in more recent, official Firefox releases but no longer in Mypal 68.14.5b. And I totally forgot to show in the clip that a left-click onto an extension opens its Options. Even uninstalling extensions can be done via this script. In short, a fast Add-ons Manager in the form of a toolbar button.

The Process Mode Toggler custom button has been originally developed for my personal use only. So, no download link is available at the moment as it is not released so far. And if Mypal 68 doesn't support the Custom Buttons extension any longer, then there will never be a release of this button. It's up to @feodor2 what will happen next. BTW, my Restart & Purge v2.0 custom button is a unique one for convenient clearing of the Startup Cache via one click. This is very important for all users of UC.JS scripts to make them run correctly after code or script changes.

To get back on topic, I am a true, daily Windows XP user. I have very special UC.JS scripts (created by a great German Firefox community) running in Mypal 68, some of which I had to customise for the now obsolete Mypal 68 browser. I have also developed nice and more complex custom buttons especially for Mypal 68. I will produce a clip to give you an impression of my configuration and work. I have already posted a clip with my new Process Mode Toggler custom button. I don't know if you've looked at it yet. https://msfn.org/board/topic/183657-mypal-68-in-windows-xp-custom-buttons-and-extensions/?do=findComment&comment=1275047

Noted. I missed that part of the conversation. Apologies. Accepted. Such misunderstandings can happen. You know, I am a man of clear words. Then send it to me in Germany!

Sorry. It seems you really don't get it. The Custom Buttons extension works in the official Firefox releases in general, even in the latest versions. And so do my and other custom buttons created with this extension. If the latest version of Mypal 68 no longer supports this extension, then that is actually an issue that does not even occur in the official Mozilla versions. And you won't understand the problem if you are not a user of Mypal 68 and this extension. You are a Chrome/Chromium user and has abandoned Windows XP. Your self-created, proprietary buttons have nothing to do with this topic and are totally irrelevant. It's not about stopping software development, but rather about steering it in the right direction so as not to act even worse than Mozilla does. And for someone who hates raccoons 🦝, has never really been involved with Mypal 68 and is no longer a user of Windows XP, I don't understand what you're actually trying to accomplish here.

@feodor2 As I already suggested, I will send you via PM an archive with the most recent Custom Buttons extension, the no longer working UC.JS scripts together with a CSS stylesheet which has the task to style the toolbar button generated by one of the scripts. Everything works fine in Mypal 68.14.4b and has stopped working in Mypal 68.14.5b. And forget about xiaoxiaoflood. This is simply crap. I have tested it deeply, and this method for loading legacy extensions and scripts cannot do anything valuable in Mypal 68 except failing. I forgot to mention that for testing purpose only, you have to use a much better loading method for scripts and CSS stylesheets I already provided in my thread in the first post when starting the thread. I will configure the archive in a way you only have to copy all files to the correct locations of your fresh installation and profile folder. Install it first in Mypal 68.14.4b and then in Mypal 68.14.5b! You will then see the problems I have been talking about. BTW, all my implementations do not generate any errors in the Browser Console in Mypal 68.14.4b since I have fixed all of them. P.S.: Archive file already sent via PM last night.

@feodor2 As I already suggested, I will send you via PM an archive with the most recent Custom Buttons extension, the no longer working UC.JS scripts together with a CSS stylesheet which has the task to style the toolbar button generated by one of the scripts. Everything works fine in Mypal 68.14.4b and has stopped working in Mypal 68.14.5b. And forget about xiaoxiaoflood. This is simply crap. I have tested it deeply, and this method for loading legacy extensions and scripts cannot do anything valuable in Mypal 68 except failing.

You don't get it. The Custom Buttons extension has stopped working completely. So, none of my custom buttons can be used anymore.

Unfortunately, your changes broke UC.JS scripts which actually work in more recent Firefox versions. Same applies to CSS stylesheets. The main toolbar is broken. The Add-ons Manager can't be accessed anymore via a well-known and great script due to the sudden script breakage. And the most recent version of Custom Buttons has stopped working in Mypal 68.14.5b in contrast to more recent Firefox versions. Same applies to earlier versions of Custom Buttons. So, yes, scripts and the Custom Buttons extension work in more recent Firefox versions but not in Mypal 68.14.5b.

I don't think that the end-user is in the position to dictate anything in development of software. But if many things are suddenly broken, then the end-user is allowed to report issues, to express his displeasure and to voice his ideas. In any case, Mypal 68.14.5b is unfortunately a failure. Nothing more and nothing less. And when it comes to me, I created and modified many things for Mypal 68. A lot of them do not work anymore in Mypal 68.14.5b. Thus, I am not amused at all. Compatibility is my top priority. So, spoken for me only, I thankfully do without a Mozilla-like development strategy. I've had enough of that. That's why I'll definitely stay with Mypal 68.14.4b if nothing is changed.

@feodor2 Inside the omni.ja file, you changed, for example, the chrome://browser/content/browser.xul file in Mypal 68.14.4b to the new chrome://browser/content/browser.xhtml file in Mypal 68.14.5b. Without any announcement and information, such changes are predestined to cause problems. Now, nothing surprises me anymore. Edit: I removed the image with a toolbar and icon issue as it was caused by one of my scripts which is now broken in Mypal 68.14.5b.

Just for clarification. I did not and do not have any problem with closing tabs or memory consumption. I use Mypal 68.14.4b in multiprocess mode with rebased DLL files. I set up my profile perfectly. In the background, a custom button is minimising memory every 10 minutes and tabs can be completely discarded at any time, either automatically or manually. I replaced many extensions by self-created or modified custom buttons and UC.JS scripts. I am not a tab horder, so I do not have any problems with memory management although my Windows XP machine is equipped with a single core CPU and only 1.5 GB SD-RAM. All is working fine , only some websites do not work anymore due to bloated, modern layouts. Greetings from Google and their frameworks, webkits & co! These websites are fodder for my Android (Google ) tablet.