AstroSkipper

Why don't you post problems with New Moon and Serpent in @roytam1's thread? It doesn't really make sense to open a new thread for this. You are also much more likely to get an answer there.

After reading your post, I have checked the HideTabbarWithOneTab.uc.js script in Mypal 68.14.8b. You're right, it stopped working. As the code of this script is not really a brummer , I decided to write a new script from scratch. I have tested it, and it now seems to be working in the way as it should. I also solved the handling of the New Tab button If you are interested in, I am quite willing to upload it. Although I prefer the Alice0775 script loader, it even works with the xiaxiaoflood one. Mypal 68.14.7b is a quite stable release and has the advantage of still supporting the Nuchi-Sporif script loader.. Some errors have crept into @feodor2's new release Mypal 68.14.8b. The Add-on Manager is not fully functional, i.e. partially broken. Furthermore, the display of elements is not always as it was in the previous version. However, I would stay away from Mypal 68.14.5b. This one is neither fish nor fowl. If I wanted to use an older version, I would rather prefer Mypal 68.14.7b or Mypal 68.14.4b. But I use Mypal 68.14.8b at the moment. Regarding MediaFire, this service works fine here. No problems.

I have found the cause of this problem. In contrast to Alice0775 version of the rebuild_userchrome.uc.js script, the xiaoxiaoflood one does not like certain characters in the script file names such as the + sign.

About the xiaoxiaoflood script loading method in Mypal 68.14.8b With Mypal 68.14.8b, @feodor2 has unfortunately retired the best script loader forever. The Nuchi-Sporif script loading method as well as all other Nuchi based script loading methods no longer work in this Mypal 68 browser and logically in upcoming releases. This means that the first three script loading methods from my ranking list are no longer available in Mypal 68.14.8b and up. @feodor2 recommends the xiaoxiaoflood script loader from the seventh and last place of my ranking list for users of xiaoxiaoflood's stuff. I have therefore taken another look at this method in Mypal 68.14.8b. As already mentioned, I am currently using the Alice0775 script loading method in this browser, which I put together, fixed and modified myself. It has a good compatibility with existing scripts comparable to the Nuchi-Sporif script loading method. Of course, I first adapted my scripts to the JavaScript changes made in Mypal 68.14.8b. I now have all my important scripts, 24 in total at the moment, running successfully with this script loader. Due to a further, small modification I made to the Alice0775 script loader, all my scripts are again located in a chrome subfolder called Scripts. BTW, more than half of these scripts were created by myself and written to be as compatible and universal as possible. Now to xiaoxiaoflood. I downloaded the version of this script loader @feodor2 recommends on this GitHub site: https://github.com/Feodor2/Mypal68/releases/tag/68.14.8b. After setting up the xiaoxiaoflood script loader in a fresh installation of Mypal 68.14.8b with a brand new profile, I copied all my 24 scripts into the chrome folder. Unfortunately, only less than half of them were ready to use after starting the browser. The xiaoxiaoflood script loader can't do anything with my most important scripts , which in contrast work perfectly with every other script loading method . Besides the already mentioned Alice0775 script loading method, also with the Aris-t2/Ardiman-Endor8 or pure Endor8 script loading method. Furthermore, it reports in the Browser Console that certain variables such as gClipboard are not defined and does not understand some JavaScript commands such as style.backgroundSize and so on at all. In addition, problems with scripts that cannot be loaded are not logged in the Browser Console. No information! Nasty! All in all, the xiaoxiaoflood script loader failed my test once again and cannot be recommended by me for general use. All other script loading methods are much better. To be unbiased and fair , I also tested this method with xiaoxiaoflood's own scripts. These special but very few scripts basically seem to work fine. But when using external scripts with this method, the xiaoxiaoflood version of the rebuild_userchrome.uc.js script, for example, is not able to handle them correctly. It is able to disable non-xiaoxiaoflood scripts but can't enable them again. Spoken for me only, I do not consider most of the very few xiaoxiaoflood scripts on offer to be particularly useful. The xiaoxiaoflood version of the extensionOptionsMenu.uc.js script, for example, which is actually a great one, is far behind the version I use which provides much more functionality. One thing is clear. There are much better scripts available outside the xiaoxiaoflood world. In general, the following should apply to a good script loader: It should be able to successfully load as many scripts as possible, taken from different sources. Needless to say, these scripts have to be compatible with the JavaScript engine of the browser used. Conclusion: The xiaoxiaoflood script loading method has very poor script compatibility for scripts that have not been written specifically for this method, does not understand some standard variables, also does not recognise some JavaScript commands and does not log successful respectively unsuccessful loading of scripts in the Browser Console. The latter is particularly annoying when scripts cause problems and the cause needs to be investigated. An error message would be desirable and helpful. This script loading method can therefore not be recommended for Mypal 68 as a general script loading method. Especially not when much better script loading methods are available. However, for those who only want to use xiaoxiaoflood's stuff, it is ok. For all others, the xiaoxiaoflood script loading method is definitely not to be recommended. Greetings, AstroSkipper

Ok. Then I'll try to answer the question about the compatibility first of all with the example of extensions in Mypal 68 myself. Unfortunately, my answer has to be: No. Mypal 68.14.8b does not have a clear compatibility policy. Even some extensions that are actually FF68 compatible do not work for various reasons. One of them is the fact that Mypal 68 has never been a complete Firefox 68 version. Consider, for example, the still missing Internationalization & Localization feature I reported to Mypal's issues on GitHub three years ago that, however, some extensions, for example those dealing with time, date, timezones and so on, definitely require. uBlock Origin 1.62, on the other hand, works in Mypal 68.14.8b, although it is actually FF78+ compatible. Another example is the Scratchpad 0.7.1 extension. Since @feodor2 has removed the very useful, internal Scratchpad in Mypal 68.14.8b following Mozilla , I wanted to retrofit it with the help of this extension, which is FF72+ compatible. Unfortunately, that didn't work out. Not compatible. In Firefox 74, however, it works. So, Mypal 68.14.8b and extension compatibility is rather a game of trial and error. MinVersion numbers of extensions are only of limited use in this browser. At this point, I would personally appreciate a Mypal 68 browser with a state of development of 74 announced by its developer that then also should behave like its brother Firefox 74 in terms of compatibility. Strictly according to the motto: Whoever says A, must also say B. (German saying) And that's completely independent of whether I like these newer Firefox versions or not.

Which official MyPal extension page? There is none. Extensions for Mypal 68 have to be downloaded from the official Firefox Add-ons page, i.e. from addons.mozilla.org.

Forget the about:performance page! It has never been reporting memory usage correctly and reflecting the true values. Here is a comment from a developer: https://bugzilla.mozilla.org/show_bug.cgi?id=1744869 And a quote from there: I can confirm this statement. It always has been a junk feature.

@feodor2 In case it has escaped your attention, here is my question again:

@feodor2 Thanks for the information! So, does that mean Mypal 68.14.8b is at the same level as Firefox 74, behaves in the same way and extensions with a minVersion of 69 up to 74 now should also work in your browser? For all, who have to fix those UC.JS scripts, CSS stylesheets and custom buttons that no longer work, the knowledge about decisive changes from 68 to 74 is important for being able to make all the necessary modifications. Therefore, it is not "unnecessary junk information". Some time ago, I already had researched all the essential changes. And as far as I'm concerned, I had to fix a lot. Fortunately, I am almost through with that.

@feodor2 Ok. Now, your fix seems to be working. At least, the code editor has started again to behave as usual. The reason it didn't work before was when purging the startup cache, then the code editor becomes inaccessible and a normal restart has additionally to be performed. However, I modified the fix a bit to depend on the current platformVersion instead of a static number. For this purpose, I had to insert one additional line. The code posted beyond is the part from line 1 to 59 of the SelfHelper.jsm file. The changes are located in line 55 and 56: var EXPORTED_SYMBOLS = ["SelfHelper"]; var AC, SelfHelper = { data: { "chrome://custombuttons/content/editor.xul": { 65: "groupbox", 68: "ondialog", 71: "textbox menulisticonic cbeditor", 76: "input", 77: "menulist", 85: "fluent", 108: "contentbox", 109: "menulist109", 113: "flexapocalypse", 116: "wrapwidth", 125: "picker" }, "chrome://custombuttons/content/prefs.xul": { 65: "groupbox", 68: "ondialog", 107: "checkbox", 111: "dialogwidth", 113: "flexapocalypse" }, "chrome://custombuttons/content/dialogs/finddialog.xul": { 65: "groupbox", 68: "ondialog", 71: "textbox", 76: "input", 107: "checkbox", 111: "dialogwidth", 113: "flexapocalypse" }, "chrome://custombuttons/content/dialogs/cbpromptdialog.xul?type=checkbox": { 65: "groupbox", 68: "ondialog" }, "chrome://custombuttons/content/dialogs/cbpromptdialog.xul?type=radiobox": { 65: "groupbox", 68: "ondialog" }, "chrome://custombuttons/content/dialogs/replconfirm.xul": { 68: "ondialog", 111: "dialogwidth" }, }, noop() {}, get map() { var {AppConstants} = AC || ChromeUtils.import( "resource://gre/modules/AppConstants.jsm" ); var {platform} = AppConstants; this.platform = ["win", "linux", "macosx"] .includes(platform) ? platform : "linux"; var { Services } = ChromeUtils.import("resource://gre/modules/Services.jsm"); this.version = parseInt(Services.appinfo.platformVersion); if (this.version >= 95) { var pref = "extensions.custombuttons.prefersColorSchemeOverride"; var pb = Cc["@mozilla.org/preferences-service;1"].getService(Ci.nsIPrefBranch); Thanks for the temporary fix! I hope you can fix your browser in terms of the versions problem soon.

Once again, this is the new code from line 1 to 58: var EXPORTED_SYMBOLS = ["SelfHelper"]; var AC, SelfHelper = { data: { "chrome://custombuttons/content/editor.xul": { 65: "groupbox", 68: "ondialog", 71: "textbox menulisticonic cbeditor", 76: "input", 77: "menulist", 85: "fluent", 108: "contentbox", 109: "menulist109", 113: "flexapocalypse", 116: "wrapwidth", 125: "picker" }, "chrome://custombuttons/content/prefs.xul": { 65: "groupbox", 68: "ondialog", 107: "checkbox", 111: "dialogwidth", 113: "flexapocalypse" }, "chrome://custombuttons/content/dialogs/finddialog.xul": { 65: "groupbox", 68: "ondialog", 71: "textbox", 76: "input", 107: "checkbox", 111: "dialogwidth", 113: "flexapocalypse" }, "chrome://custombuttons/content/dialogs/cbpromptdialog.xul?type=checkbox": { 65: "groupbox", 68: "ondialog" }, "chrome://custombuttons/content/dialogs/cbpromptdialog.xul?type=radiobox": { 65: "groupbox", 68: "ondialog" }, "chrome://custombuttons/content/dialogs/replconfirm.xul": { 68: "ondialog", 111: "dialogwidth" }, }, noop() {}, get map() { var {AppConstants} = AC || ChromeUtils.import( "resource://gre/modules/AppConstants.jsm" ); var {platform} = AppConstants; this.platform = ["win", "linux", "macosx"] .includes(platform) ? platform : "linux"; this.version = 74; if (this.version >= 95) { var pref = "extensions.custombuttons.prefersColorSchemeOverride"; var pb = Cc["@mozilla.org/preferences-service;1"].getService(Ci.nsIPrefBranch); Is that correct? You should think carefully about what you say. None of what I have written is spam or flame. Do you even know what spam or flame means or is? However, your statement I quoted above comes closer to that. Politeness doesn't seem to be everyone's cup of tea. Anyway! Can you finally explain why the Custom Buttons extension properly works in Firefox 74 without any fix but not in Mypal 68.14.8b? Just a wrong version number which your browser reports to the Custom Buttons extension at a certain point as I assumed at the beginning?

I tried your fix. If I have understood you correctly, in the SelfHelper.jsm file, I should replace line 55 this.version = parseInt(AppConstants.MOZ_APP_VERSION); with the following one: this.version = 74; If so, then this does not fix anything. The only thing that happens is a lot of new ReferenceError messages "Service is not defined" in the Browser Console. Furthermore, I think that it is not the Custom Buttons extension that needs to be fixed, which runs properly under Firefox 74, but Mypal 68.14.8b. What do you mean by "hubbub"? Did you even read what I wrote? I consider such an answer to all my information, investigations and questions that I have put a lot of effort into to be absolutely inadequate. I have asked you a few questions, but have not received any answers. And once again, I no longer think the issue is related to a version mismatch. All is explained in the posts above and in my thread "Mypal 68 in Windows XP". Keyword: XBL But I will not repeat myself here.

@feodor2 I'm afraid that you've overshot the mark with your changes as you did in version 68.14.5b. With a probability bordering on certainty, there will be other "patients" who suffer from similar "symptoms" as is currently the case with Custom Buttons. Whatever the actual cause, I hope I could help you with my investigations and information.

@feodor2 Although Mozilla does and has done things to their Firefox browser for years that I personally think are terrible, certain features, even if they are considered deprecated and not secure, will be retained for compatibility reasons. That's something positive. On the subject of XBL and binding, what about the CSS property -moz-binding in your new release? This property is also used by Custom Buttons. For example, for the code editor in the file codeeditor-cbeditor.css: cbeditor { -moz-binding: url(chrome://custombuttons/content/cbeditor.xml#custombuttons-codeeditor); } #accelkey { -moz-binding: url(chrome://custombuttons/content/cbeditor.xml#accelkeytextboxbinding); } Can Mypal 68.14.8b even cope with this?

Thanks for your reply! I investigated the code of Custom Buttons more deeply, and you are right, the Custom Buttons extension solely relies on the platformVersion, Since you removed the XUL stuff, you logically can't keep the platformVersion at 68. But your new release Mypal 68.14.8b has become somehow versionless. It doesn't behave as a Firefox 68 and it doesn't behave as a Firefox 74. It's a bit lost. Your browser tells Custom Buttons that it is Firefox 74, but it is not. Today, for this purpose, I have made a proof and installed Firefox 74 Portable on a Windows 7 Professional 64-Bit notebook, injected the two files config-prefs.js and config.js, and installed the legacy Custom Buttons extension. As I have already predicted, Custom Buttons runs perfectly under Firefox 74. The code editor is fully functional. The legacy Custom Buttons extension has always been compatible with much newer Firefox versions and is constantly being developed further. Here are two screenshots to demonstrate what the issue is about: Custom Buttons' broken code editor in Mypal 68.14.8b: Custom Buttons' fully functional code editor in Firefox 74.0.1: As I already said, you must have removed something that Mozilla did not. And I suspect it has something to do with XBL. Certain functions for binding XML files are required by the Custom Buttons extension for the code editor, which you have probably removed. That's why I said your new release is somehow versionless. Neither fish nor fowl. Sorry for that! The conversion from XUL to XHTML is no problem as you can see. Anyway! I hope you won't behave worse than Mozilla did in the past, and I urgently hope you will be able to restore a general version compatibility. And it doesn't matter which Firefox version you raise the platformVersion to as nevertheless the Custom Buttons extension should work then.

In comparison to Mypal 68.14.8b, I have executed the two JavaScript commands again in Mypal 68.14.7b: JavaScript commands: parseInt(Services.appinfo.platformVersion); Output: 68 parseInt(Services.appinfo.version); Output: 68 In any case, there is a clear version specification in the previous release.

Sorry but unfortunately, I have to disagree when it comes to Windows XP -> Windows NT 5.1 and Mypal 68. As you know, this topic here is about Mypal 68 in Windows XP . I have tested all possible Firefox version numbers by a SSUAO in Mypal 68.14.8b, and 128 was definitely the minimum to get rid of the yellow message box. Any version lower than 128 failed. Greetings, AstroSkipper

Here are some facts about versions inside Mypal 68.14.8b: JavaScript commands: parseInt(Services.appinfo.platformVersion); Output: 74 parseInt(Services.appinfo.version); Output: 68 ------------------------------------------ Some preferences in about:config: browser.migration.version: 94 extensions.lastAppVersion: 68.14.8 ------------------------------------------ General user agent: Mozilla/5.0 (Windows NT 5.1; rv:88.0) Gecko/20100101 Firefox/88.0 Mypal/68.14.8 68, 74, 88, 94 Neither fish nor meat (German saying). Or, neither fish nor fowl. The problem with this is that there have been some significant changes in the Firefox versions from 69 to 72. If an extension receives the wrong Firefox version at a certain point, this can of course lead to malfunctions. And that's exactly what I think might be the case with the Custom Buttons extension. The other theory, that something elementary has been removed, of course remains. Strangely enough, a few typical error messages relating to the cbeditor.xml file have completely disappeared. Maybe, this file can't be correctly processed now. Possibly due to @feodor2's remove of XBL?

Ok. This issue seems to belong to all old browsers. To get rid off this yellow message box, you need an updated user agent. Firefox 128 is now the minimum under Windows XP: Mozilla/5.0 (Windows NT 5.1; rv:128.0) Gecko/20100101 Firefox/128.0

@feodor2 Due to the changes in Mypal 68.14.8b, the Firefox Add-ons page shows the yellow message box even with compatible extensions "You need an updated version of Firefox for this extension". Here, for example, is the extension TWP - Translate Web Pages whose latest version 10.1.1.1 has a minimum version of 64: https://addons.mozilla.org/en-US/firefox/addon/traduzir-paginas-web/ TBH, this message is now displayed on all extension pages, and it doesn't matter whether the extension is compatible or not. So, what's going on here? Somehow, your browser seems to have become versionless.

@feodor2 Thanks for your new release Mypal 68.14.8b! I am currently testing this version more closely. Due to the complete removal of XUL and XBL, a lot has changed. I have already reported about it here. Similar to version Mypal 68.14.5b, the legacy Custom Buttons extension is no longer fully functional. The internal code editor is totally broken and therefore has become unusable. You can no longer access, view or edit the code with the extension. New custom buttons can't be created, either. The legacy Custom Buttons extension should actually also work in higher Firefox versions. It has corresponding XHTML files and compatible code that is made available via appVersion queries. It could be that an incorrect version is being determined, as version 68 or version 74 is displayed in Mypal 68.14.8b depending on the corresponding command. I checked that in the Browser Console. BTW, I really miss the Scratchpad which is also gone in your new release. Another guess I have is that you have removed something important that requires the legacy Custom Buttons extension. As you know, in Mypal 68.14.7b, the legacy Custom Buttons extension still worked. Maybe, you can take a look at it. BTW, what is the current level of JavaScript and CSS in Mypal 68.14.8b?

FYI, the Nuchi-Sporif UC.JS script loader, the best script loading method so far, presented in the first post of this thread for years, has stopped working with @feodor2's new release Mypal 68.14.8b. All other methods based on the Nuchi script loader won't work anymore, either. The Xiaoxiaoflood script loading method which is now recommended by @feodor2 is unfortunately the worst of all methods tested by me some months ago. I won't use it in any case and have changed to the Alice0775 script loading method in 4th place in my ranking list. Several scripts don't work anymore and have to be fixed due to all changes. Same applies to CSS stylesheets. I have already adapted a whole series of both to the "new" Alice0775 script loading method and to the new browser. @feodor2 seems to have removed XUL and XBL from Mypal 68.14.8b. Although the legacy Custom Buttons extension still can be installed, it is now somewhat broken. The internal code editor completely stopped working. And as expected, Xiaoxiaoflood's extension loader can't help either. That would have been a miracle if it had been different. I wish everyone lots of fun fixing scripts and stylesheets.

Thanks for replying! This is just a leftover and has now been edited by me. But the other announcements are correct and point to the most recent version.

A night's sleep always brings new ideas to light. The 7-Zip commands for extracting can be simplified to remain completely relative in the path information such as I already did in the whole ytBATCH for Windows XP script ensemble. I will implement this in the next release. Sometimes, things are that simple.

@Cixert Both your system error 3 and the message "permission denied" do not happen here in any case and therefore can't be reproduced by me. They seem to be related to your system only. So, solving that is up to you. On the other hand, the inability of correct unzipping on your drive D: was caused by a 7zip command which was actually relatively created by me but was unintentionally bound to drive C: exclusively. However, this had no negative effect on standard computers with C: as the system drive. That's why I didn't notice it. Anyway! ytBATCH for Windows XP should now be able to be set up automatically and without any errors (at least, no erros caused by ytBATCH for Windows XP), even on a non-standard computer as yours. Thus, thanks again for your report here and for being non-standard!