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?

Today, I have installed and tested Mypal 74.1.0. @feodor2, thanks for this new version and for cleaning up the version number chaos! Good job! My favoured Alice0775 script loading method still works with this browser version as I have predicted in previous posts. And I am very pleased that the Custom Buttons extensions and all my self-created scripts also work there. However, one issue is still present in Mypal 74.1.0. Clicking entries in the Add-ons Manager does not work yet and leads to the well-known message that the address is not understood.

I'm glad you like my article. Creating it and making the HTTPSProxies more future-proof was a pleasure for me as a die-hard fan of Windows XP.

You can find the download link for the CAupdater in my main article ProxHTTPSProxy and HTTPSProxy in Windows XP for future use in the section 11.2.4. Downloads related to Root Certificate Updates.

Hide Tab Bar If Only One Tab - A UC.JS script for hiding the tab bar if only one tab is present and positioning the new tab button before the search bar As part of my JavaScript and CSS studies , I have been working on hiding the tab bar in Mypal 68 when only one tab is open in the browser, purely for practice purposes. For this endeavor, I was able to develop a number of solutions based on different methods: A purely CSS-based method (variant 1) A purely CSS-based method (variant 2) A purely JavaScript-based method using a mutation event A purely JavaScript-based method using a mutation observer (variant 1) A purely JavaScript-based method using a mutation observer (variant 2) A JavaScript-based method with embedded CSS (variant 1) A JavaScript-based method with embedded CSS (variant 2) I will present the result of my work here today in the form of method 6. Although all methods have their right to exist and conserve resources, methods 1, 2, 6 and 7 are by nature the least taxing on the processor. So, why a JavaScript-based method with embedded CSS instead of a purely CSS-based one? The answer is easy. The purely CSS-based method works fine when it comes to hiding the tab bar in Mypal 68 when only one tab exists but the new tab button is then no longer visible. If you don't need this button, the purely CSS-based method is completely sufficient. But if not, you will miss this button to quickly open new tabs. That's why I created this JavaScript-based method with embedded CSS. Alternatively, when using CSS only, the user first has to manually move the new tab button to a desired location if needed. BTW, there are different CSS code snippets available for hiding the tab bar in the World Wide Web but a lot of them do not work properly in Mypal 68.14.8b. That's why I created my own code, and this as minimal as possible. My HideTabBarIfOnlyOneTabCSS-5.0.uc.js script performs the following actions. First, it positions the new tab button before the search bar. The target position for the new tab button can of course be changed by the user and requires only minimal JavaScript knowledge. Then, it hides the tab bar if only one tab is present. Additionally, this script sets a min-height adjustable by the user for the tabs depending on the density setting currently selected. BTW, all methods have been deeply tested by me and are working in Mypal 68.14.8b. I developed them with my favoured Alice0775 script loading method but they are also working with other methods, such as the Xiaoxiaoflood script loading method. Due to the permanent changes especially regarding CSS made by Mozilla and by @feodor2 who follows their guide lines, this code will definitely break one day. When this happens, I will provide another one of my solutions which will most probably also work in future releases of Mypal 68. Of course, only if there is a recognisable interest. Here is a short animation showing my script in action: This script is aimed at users who only open a few tabs or even only use a single tab. In the latter case, more space is available for the web content when the tab bar is hidden. However, for tab hoarders or tab collectors, this script will be of no use. And here is the download link for my HideTabBarIfOnlyOneTabCSS-5.0.uc.js script: https://www.mediafire.com/file/82ex3oierj09mt1/HideTabBarIfOnlyOneTabCSS-5.0.uc.js/file BTW, my other script HideTabbarWithOneTab.uc.js from August 2024 is now obsolete. It does not work in Mypal 68.14.8b and can only be used in older releases, such as Mypal 68.14.4b. Greetings, AstroSkipper

Welcome back! Not being able to continue reading where you last left off is of course annoying. I wouldn't be particularly pleased either...

Facebook & Co always throw tons of error messages in the Browser Console in New Moon 28. Awful! No interest to look deeper into it since I do not even use such services. But your linked website and video at least work in Mypal 68. BTW, after closing this site in Mypal 68 and cleaning the browser cache, residues remain, which lead to error messages in the Browser Console when switching back to the MSFN page. Only a restart with purging the startup cache provides a remedy. Facebook is simply rubbish. Anyway! Maybe, one day there will be fixes coming from MCP which then might be ported to @roytam1's browsers. @roytam1 will eventually know more details.

The animation above is based on two implementations I use in combination. A CSS stylesheet from Aris-T2 for a tab bar with multiple lines, adapted to my needs, and an UC.JS script I created from scratch for hiding automatically the tab bar if only one tab is present. This UC.JS script is unique, written by me in pure JavaScript and contains a new method I developed to automatically hide the tab bar with only one tab completely, i.e. neither an empty space nor the new tab button remain. This new code works much better than all existing solutions you can find elsewhere. It does its job in all possible cases and doesn't need additional CSS code. There are also pure CSS solutions available from different sources in the World Wide Web but in some cases, they unfortunately either fail or do not work anymore. In contrast, my method is extremely compatible to all existing modifications inside Mypal 68, which could be made by the user, and really hides the tab bar in case of only one existing tab as it is shown in the animation above. My knowledge of JavaScript and CSS, which I have acquired and deepened over the last months on an autodidactic basis, seems to be bearing fruit without end when it comes to scripts. I'm as proud as Oskar (German saying). Especially considering that I am not a programmer by nature.

Your assumption is wrong. Doesn't seem to be one of your strengths. You solely interpret, but not particularly well. All your quotations lead to the statement that it works for me. No more, no less.

Where did I claim that it always works? First of all, it works for me on my Windows XP computer (real installation on a hard disk with time-period correct, old hardware, i.e. no virtualisation). And that means that it can basically work. No more and no less.

Same here in New Moon 28. But it works in Mypal 68.