AstroSkipper

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.

In general, it's always a good idea not to make too many changes at once when it comes to software development. You don't want to end up like Mozilla, which breaks compatibility almost with every release. @feodor2 Here is my wish for Christmas: Please, recheck your changes and revert those which break compatibility! None of your previous releases caused any breakages to UC.JS scripts, CSS stylesheets, extensions or custom buttons. There was only one breakage in terms of language packs in the past. But all other things worked in every of your releases. Do not follow Mozilla's way of destruction!

After all my tests and changes I made with UC.JS scripts, CSS stylesheets, custom buttons and extensions, the best and most stable version for me is Mypal 68.14.4b.

Just for your information! All solutions, be it UC.JS scripts, extensions or CSS stylesheets, I have posted here are definitely working up to the version 68.14.4b. Unfortunately, the most recent version Mypal 68.14.5b causes breakages. (German saying. Translated: There is the worm in it!) Therefore, be careful when updating Mypal 68! A backup of your profile should be done first. Do not post here any issues regarding this version! Mypal 68.14.5b contains changes which break different things like extensions, scripts and styles. Therefore, it should be used with caution in production systems. I have installed it for testing purpose only and for reporting issues. All issues should be reported in the Mypal 68 thread or to the issues on GitHub.

The Custom Buttons extension worked fine in Mypal 68 from the very first release until the previous version 68.14.4b. @feodor2 also has this extension available and can certainly test what's going on. In any case, he has made significant changes. The menu bar is also affected and no longer behaves as it did before. This may also be one of the reasons why some of my CSS stylesheets no longer work. Same applies to the Add-ons Manager. P.S.: @feodor2 And FYI, I also tried xiaoxiaoflood's method you recently pointed to and installed the boostrapped version of Custom Buttons (this extension always comes in two different versions). In this case, the extension options appears again in the Add-ons Manager (no error in the Browser Console in terms of the boostrap.js file) but when installing custom buttons, none of them are available. Although they are listed under the entry Custom Buttons in the Add-ons Manager, they are simply not accessible and their tool bar icons missing in the Customize window. Same to the Custom Buttons menu in the main toolbar. As you may know, Custom Buttons is an extension that also runs in newer Firefox versions up to the very latest. BTW, all was tested by me in a clean, fresh profile. If you need all the no longer working stuff, please let me know. I will then upload it for you. P.S.2: Furthermore, new errors can be found in the Browser Console compared with your previous release, even when opening the about:preferences page. Since you haven't been around here since 27. October, and the bugs are plentiful and serious, I even jumped over my shadow and reported it to your issues on GitHub to make sure you were aware of the problems with your new release.

Hi @feodor2! Thanks for your new release and all your efforts to improve Mypal 68! Unfortunately, I have to report that my beloved Custom Buttons extension is no longer working due to the changes you made in Mypal 68.14.5b. Furthermore, some UC.JS scripts have stopped working. Same applies to some CSS stylesheets. All of them have been working fine in Mypal 68.14.4b but in your new release, they do not work anymore. Although the Custom Buttons extension can be installed, the extension options is missing and when installing some custom buttons, they do not appear. Neither they are listed under the entry Custom Buttons in the Add-ons Manager nor their tool bar icons are shown in the Customize window. The CB menu in the toolbar to create buttons is also missing. The Browser Console shows errors when reading the boostrap.js file of this extension. Try it yourself as you already have the Custom Buttons extension! At the moment, I will stay with Mypal 68.14.4b. Too much is not working in Mypal 68.14.5b.

The last months, I have deepened my knowledge about JavaScript and CSS. In the case of the Process Mode Toggler custom button, one might think that it only toggles the browser.tabs.remote.autostart preference. However, this is not the case. Besides toggling this preference, my custom button displays the current process mode via toolbar icon and tooltip. It doesn't matter whether the button was used for toggling the process mode or not. It always recognises the correct mode. The process mode change is linked to a restart of the browser which is of course necessary for running the browser in the new mode. Additionally, it also adjusts two other prefs that are related to the respective process mode: dom.ipc.processCount and dom.ipc.processCount.webLargeAllocation. Their values can be preset for the respective process mode in the first lines of the button code. So, this custom button is very special and rather unique. In any case, one thing is clear. Webextensions are much more restricted and not allowed to control such features what in contrast UC.JS scripts and legacy custom buttons can easily do, though.

Which two buttons? The clip is about one button, my recently created custom button called Process Mode Toggler. You won't find it anywhere. However, I have recently posted some new custom buttons for UXP browsers and compatibles in my thread "Extensions and custom buttons for UXP browsers - Corrections, modifications, adjustments, and special recommendations". Given the lack of response and interest, I doubt that the Custom Buttons extension is used very much in general by our members or readers for whatever reasons which I do not really have to understand, though. And with a probability bordering on certainty even much less in Mypal 68 if at all. TBH, I am beginning to think I am the only one using the legacy Custom Buttons extension in Mypal 68. Anyway! I developed the Process Mode Toggler custom button actually for personal use in Mypal 68 to test UC.JS scripts, CSS stylesheets, extensions and legacy custom buttons conveniently and quickly in multiprocess mode as well in single-process mode. Especially to test my self-created ones. If there was genuine interest in my custom buttons and it was communicated in this way, then things would be different. But I can't see that so far. The clip I have posted should simply give you an impression of what I do with custom buttons and what can be done at all. No more, no less.

I think it is well known by now that I am a fan of custom buttons. The last months, I created a couple of them for the UXP browsers as well for Mypal 68. Here is one of my latest creations:

Then, try for example the Auto Tab Discard extension! However, not the most recent version but the older one 0.5.0. When it comes to uc.js scripts or extensions for use in Mypal 68, it is very often better to use older versions (according to the era) due to compatibility issues. Here is the download link: https://addons.mozilla.org/firefox/downloads/file/3889015/auto_tab_discard-0.5.0.xpi Even this version shows some warnings in the Browser Console as there are features in the extension's manifest which Mypal 68 doesn't support. But this version is nevertheless fully working in Mypal 68.