Mypal 68 in Windows XP - Custom Buttons and Extensions

[dmiranda]

Quite neat button. Wonder when you will release it. Also dreaming of the multifunction about button you shocased in the upx thread. And salivate of thinking having a fre-toggler in my pal

Cheers! Edited October 25, 2024 by dmiranda

[AstroSkipper]

21 hours ago, AstroSkipper said:

As custom buttons are actually the topic of this thread, I have decided to post about this stuff here again. My project of creating a custom button to directly call up the "Manage Cookies and Site Data" dialogue in Mypal 68 seems to have come to a temporary end. It works perfectly. I have solved the issues encountered in my own way and I am currently in testing mode. Here is a short preview:

Perhaps, someone is now wondering what is so special about the "Manage Cookies and Site Data" custom button. The answer is quite simple. There is no functioning extension or toolbar button for the Quantum browser Mypal 68 that can simply call up the native, internal cookie manager only. In contrast to the UXP browsers, the direct call of the corresponding XUL file is unfortunately no longer sufficient because it doesn't work correctly. Call it a bug, an issue or whatever, in any case, it is faulty. This custom button seems to be therefore unique.  Contrary to the native popup, to which you first have to click through, It calls up the internal cookie manager by only one click in an own, resizable window. 
BTW, creating custom buttons for UXP browsers is much easier and much more fun. In the Quantum browser Mypal 68, most things no longer work as easily or at all. Everything is very restrictive and obstructed. 

Edited October 25, 2024 by AstroSkipper
Update of content

[AstroSkipper]

@feodor2 I am not sure if you aware of this. The logger of uBlock Origin 1.60 does not work in Mypal 68.14.4b when running single-process mode. Neither in the officially last compatible version 1.46 of uBlock Origin. In multiprocess mode, the logger is running fine.

[AstroSkipper]

On 10/18/2024 at 11:03 AM, AstroSkipper said:

The download package MYPAL_68_CB_requirements.7z from my first post is not available anywhere. It is very specific, and stops working in Firefox 72+ due to some code changes. I put together the configuration files myself to make it really work. In higher Firefox versions, the script functionality seems to be much easier to activate. BTW, one file of my package spits out an error in the Browser Console, which I fixed in the meanwhile. 

The download package MYPAL_68_CB_requirements.7z from my first post is actually working as it should. But I found in one file unnecessary code which was implemented by the original creator for enabling pre-Lion fullscreen mode mode under macOS. However, this code inside the file userChrome.js spits out an error in the Browser Console under Windows XP, which I could fix in two different ways. The most simple one is to remove this code since Mypal 68 targets the Windows OSes. The other one is to add some missing code which I also did just for fun. But as I already said, this is actually nonsense. Anyway! Here is the error when using the original userChrome.js file:



And here is a screenshot after removing code from the original userChrome.js file and restarting the browser:



You can see the message "ReferenceError: XPCOMUtils is not defined" has gone.  After some weeks of testing, I can confirm that all is working perfectly.  If you are interested in and want to also do the fix manually, then you can do it as follows:

Old content of the userChrome.js file:

// Copyright (c) 2017 Haggai Nuchi
// Available for use under the MIT License:
// https://opensource.org/licenses/MIT

// Set "useLionFullScreen" in the same way that it's done in
// chrome://browser/content/browser-fullScreenAndPointerLock.js
XPCOMUtils.defineLazyGetter(FullScreen, "useLionFullScreen", function() {
    return false;
});

New content of the userChrome.js file:

// Copyright (c) 2017 Haggai Nuchi
// Available for use under the MIT License:
// https://opensource.org/licenses/MIT

Additionally, I will update the MYPAL_68_CB_requirements.7z package as soon as possible.

Greetings from Germany, AstroSkipper

Edited November 22, 2024 by AstroSkipper
Update of content

[AstroSkipper]

BTW, I reorganised the chrome subfolder inside my Mypal 68 profile folder. From now on, all my uc.js script files are located in a subfolder called "Scripts" such as all css files have already been stored in a subfolder called "CSS". If someone is interested how that can be done, just ask here. 

[AstroSkipper]

Besides rebasing several DLL files and triggering the internal memory minimisation feature, there is a third option to reduce RAM consumption in Mypal 68 called discarding tabs. Tabs, which have been loaded but not used at the moment, can be successfully discarded in multiprocess mode without disappearing in the tab bar. If it is done correctly, these tabs do no longer occupy any RAM. I found a uc.js script and a few extensions which could satisfactorily fulfill this job.

Edited November 24, 2024 by AstroSkipper

[seven4ever]

I was searching such an extension for modern browser but didn't fin one.

[AstroSkipper]

3 minutes ago, seven4ever said:

I was searching such an extension for modern browser but didn't fin one.

I can't say if these extensions I found do their job correctly in modern browser. This thread is about Mypal 68 which of course isn't a modern browser. It is more an old browser modified to be a bit more recent, especially its JavaScript engine. So, do you look for such an extension targeting Mypal 68?

[seven4ever]

Yes of course, I have still Xp ...

[AstroSkipper]

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. 

Edited November 24, 2024 by AstroSkipper
Update of content

[AstroSkipper]

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:


 

[dmiranda]

Hi @Astroskipper. Where can we try these (two?) new buttons?

[AstroSkipper]

14 hours ago, dmiranda said:

Hi @Astroskipper. Where can we try these (two?) new buttons?

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. 

Edited November 25, 2024 by AstroSkipper
Update of content

[AstroSkipper]

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. 

Edited December 4, 2024 by AstroSkipper
Update of content

[AstroSkipper]

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.

Edited December 4, 2024 by AstroSkipper
Update of content