AstroSkipper

Announcement Due to the fact that @feodor2 has been working for months to ensure that the Custom Buttons extension runs smoothly, so as soon as the new version of Mypal is available, I will publish my custom button PMT - Process Mode Toggler. This custom button, now in version 7.0, allows the user to toggle between single-process and multi-process mode in Mypal with one click and appropriate, pre-selectable settings. The toolbar icon and the toolbar tip always show the current status. Since version 3.0, the PMT custom button comes with a Compatibility Service inside the script which, if activated, checks, whether the browser used is compatible with this custom button or not, and gives advices what to do to ensure that it is working there as designed. The PMT - Process Mode Toggler custom button is in any case compatible with all versions of Mypal 68 and Mypal 74 released until now.

New, temporary fix for the Custom Buttons extension in Mypal 74.1.1 A temporary fix can be done In line 782 of the bootstrap.js file and in line 36 of the addons-html.js file inside the extension: - means remove + means add ************** In line 782 of the bootstrap.js file: - if (!FOX85 && appVersion >= 78 && url == "chrome://custombuttons/content/overlay.xul") + if (!FOX85 && appVersion >= 74 && url == "chrome://custombuttons/content/overlay.xul") In line 36 of the addons-html.js file: - if (version >= 78) { + if (version >= 74) { The latter fix of the addons-html.js file comes from @feodor2. Alternatively, you can follow his instructions for patching here: https://github.com/Feodor2/Mypal68/issues/426#issuecomment-3172415836 Now, the list of all installed custom buttons appears again.

@DrWho3000 I have abandoned Thorium months ago due to the lack of updates. At that time, I used a ThoriumLoader.exe and a ThoriumLoader.ini file customised by implementing the Thorium Icon Set. If interested, I can upload both files for further use. I do not have any use for it anymore. You still have to adapt the ThoriumLoader.ini file to your needs, of course.

Thanks! This works. The list of all installed custom buttons appears again. So, I was spot on with the addons-html.js file. Anyway. One of the two "Uncaught - undefined" error messages has thus been fixed, however, the other one still remains. That means clicking onto the entry Custom Buttons in the Add-ons Manager for opening its list leads to only one error message each time in Mypal 74.1.0 instead of two from now on. Time will tell whether this remaining error has a negative impact, too.

Alternatively, you can create custom rules for the AVSForum. uBO's logger will tell you which rule is the causer. But TBH, I do not use the Phishing URL Blocklist anyways. But I think there will be more and more filter lists coming up with certain rules no longer working properly in such old versions of uBO.

Temporary fix for the Custom Buttons extension in Mypal 74.1.1 A temporary fix can be done In line 782 of the bootstrap.js file inside the extension: In line 782 of the bootstrap.js file: - if (!FOX85 && appVersion >= 78 && url == "chrome://custombuttons/content/overlay.xul") + if (!FOX85 && appVersion >= 74 && url == "chrome://custombuttons/content/overlay.xul") However, the list itself of all installed custom buttons is still empty. But this is caused by one of the unfortunately undocumented changes @feodor2 did in Mypal 74.1.0.

@Monroe Actually, uBO 1.62 is compatible with FF78 and up. And uBO 1.65 is compatible with FF92 and up. But as @feodor2 wrote, one can't rely on version numbers in Mypal anymore, it is now a mix of different ones. So, only trial and error is the game. Personally, I prefer uBO 1.62 at the moment since I don't want to go too far away from FF68 or FF74. Who knows what would be missing if you moved too far away from FF68 in terms of compatibility. OTOH, do not think if something is compatible with FF68, it has to work in Mypal. That's water under the bridge. Think, for example, of the Nuchi-Sporif script loading method which no longer works in Mypal! P.S.: This and the last few posts are an exception. Everything concerning extensions, custom buttons, CSS stylesheets or UC.JS scripts and their loaders in Mypal will be dealt by me with in this dedicated thread: I personally consider this thread here for the Mypal browser itself. At the moment, my favourite version of Mypal is 68.14.8b.

uBO can be installed in Mypal 74.1.1 and is working there. Here is a screenshot showing that uBO 1.62 is installed: I was also able to install the latest version 1.65. And TBH, there are no other adblocker extensions comparable with uBO.

@feodor2 This is how the list of all installed custom buttons should look like inside the Add-ons Manager if all is fine. This screenshot comes from Mypal 68.14.8b, the last version where the Custom Buttons extension is fully working and the Add-ons Manager seems to be more stable: P.S.: BTW, clicking extension entries in the Add-ons Manager does not work in single-process mode of Mypal 74.1.1 and leads to the well-known message that the address is not understood. OTOH, in multi-process mode, it seems to be working.

Just for clarification. Editing the bootstrap.js in the way I described above makes the Custom Buttons extension working again. All my self-created custom buttons and the button editor are working as it should be. Only the list of all installed custom buttons inside the Add-ons Manager is broken as already in Mypal 74.1.0. @feodor2 To avoid a general setting to appVersion 78 the fix can also be done in the line you referred to: In line 782 of the bootstrap.js file: - if (!FOX85 && appVersion >= 78 && url == "chrome://custombuttons/content/overlay.xul") + if (!FOX85 && appVersion >= 74 && url == "chrome://custombuttons/content/overlay.xul") This is working too, and even the icon of the custom buttons list appears again. However, the list itself is still empty. But this is caused by one of the changes you did in Mypal 74.1.0. Maybe a CSS related change? One thing is clear. Nobody but you will be able to answer that, because only you know exactly what has been changed since Mypal 68.14.8b. And your provided changelog for Mypal 74.1.0 is unfortunately too common and unspecific (marked red) to get an idea what's going wrong: P.S. 1: Alternatively, another theory. You changed in Mypal 74.1.0 the appVersion from 68 to 74. Maybe, the Custom Buttons extension expects further features of an FF74 browser elsewhere, which are unfortunately not available in Mypal 74.1.0, which is why the list of all installed custom buttons in the Add-ons Manager cannot be built. Has, for example, Bug 1525175 - [about:addons] Move header into HTML views (Firefox 72+) (https://bugzilla.mozilla.org/show_bug.cgi?id=1525175) already been fixed in Mypal 74.1.0? I found this in the addons-html.js file, which is involved in building the list in the Add-ons Manager, located inside the Custom Buttons extension. P.S. 2: When clicking onto the entry Custom Buttons in the Add-ons Manager for opening its list, I get each time this error message in Mypal 74.1.0: Unfortunately, a very unspecific error message that usually refers to an unhandled exception in JavaScript code causing a script called up to stop executing and potentially break the functionality of the corresponding page which in this case is the Add-ons page. That would fit in well with my theory in P.S. 1 I put forward earlier. But maybe, you can find out the exact cause for it. What I can say for sure is that I don't get this error message in Mypal 68.14.8b.

Just for clarification. Editing the bootstrap.js in the way I described above makes the Custom Buttons extension working again. All my self-created custom buttons and the button editor are working as it should be. Only the list of all installed custom buttons inside the Add-ons Manager is broken as already in Mypal 74.1.0.

Yes, it is about Bug 1609556 - Migrate toolbar-context-menu to Fluent (Firefox 78+) comment this one below inside the addon if (!FOX85 && appVersion >= 78 && url == "chrome://custombuttons/content/overlay.xul") Shall consider to put the version 78 then Thanks for replying! And yes, editing the bootstrap.js file inside the Custom Buttons extension causes my custom buttons to reappear, the editor to work again and the options menu to be available again. I did the following: In line 66: - this.appVersion = parseInt(Services.appinfo.platformVersion); + this.appVersion = 78; Not working, being completely empty and not showing its icon is the list of all custom buttons in the Add-ons Manager: Unfortunately, totally broken. Maybe, you have an idea to fix this. Mypal 68.14.8b was the last version where the list worked correctly.

@feodor2 New issue in Mypal 74.1.1: https://msfn.org/board/topic/183657-mypal-68-in-windows-xp-custom-buttons-and-extensions/page/27/#findComment-1281511 Old, well-known issue in Mypal 74.1.0: https://msfn.org/board/topic/183657-mypal-68-in-windows-xp-custom-buttons-and-extensions/page/27/#findComment-1281185 And a question you didn't reply to: https://msfn.org/board/topic/183657-mypal-68-in-windows-xp-custom-buttons-and-extensions/page/27/#findComment-1281186

The Custom Buttons extension has been working basically in Mypal 74.1.0, only the list of all installed custom buttons in the Add-ons Manager has been empty and the Options menu in the Add-ons Manager was not shown. Unfortunately, the Custom Buttons extension now stops working completely in Mypal 74.1.1. No custom buttons appear, and the button editor is broken.

Now, after @feodor2's versions cleanup, I was able to install Scratchpad 0.7.1 in Mypal 74.1.0 as a replacement for the removed, internal Scratchpad but it doesn't work as intended. The Scratchpad window is partially broken. No possibility to run JavaScript code. From this I conclude that Mypal 74 is not yet at the level of FF 72 or even 74 when it comes to extensions. @feodor2, am I right?