Search the Community

Mypal 68 in Windows XP – Custom Buttons, Extensions, UC.JS Scripts, and CSS Stylesheets @feodor2 created a great new browser called Mypal 68, a browser for Windows XP based on Firefox 68. It is still in development. Here is the link: https://github.com/Feodor2/Mypal68. Mypal 68 is the first one which bases on Firefox Quantum targeting Windows XP. We already have a thread about Mypal 68 generally. It is here, started by @Jody Thornton: https://msfn.org/board/topic/183495-mypal-68/. Logically, we will stick with this browser in Windows XP for a long time. The goal of this thread is to make this browser as comfortable as possible and to enhance its functionality. Purpose and structure of this thread All Pale Moon, New Moon and abandoned Mypal browser editions support old legacy UXP-based extensions. In contrast to them, the new Mypal 68 is a browser which actually only supports webextensions, like Firefox editions 57+. Therefore, all our beloved legacy extensions can't be used anymore except those ported to webextensions by their developers. Especially all custom buttons extensions don't work anymore and there are no replacements among the webextensions. In the past I created some custom buttons by using JavaScript, but none of them can be loaded in Mypal 68. Starting from Firefox 57, we have to notice following rule: the higher version, the more restricted in customization of the browser's UI and its functions. And if you think, all of these new webextensions will work in Mypal 68, then you will be disappointed once again. And exactly that is the reason I created this thread. The purpose of it is on the one hand to collect and provide information about useful, fully working extensions and on the other hand to show alternatives for implementing custom buttons, all in Mypal 68. The idea is one useful, fully working custom button or extension, one post. Custom buttons in Mypal 68 The implementation of a custom button into Mypal 68 is much more complicated than it was in the case of UXP-based browsers. As already stated, all old custom button extensions don't work anymore. The same applies to created custom buttons targeting these CB extensions. There are no replacements among the webextensions. So what can we do? The answer is using scripts. In the profile folder of Mypal 68 a new subfolder "chrome" has to be created if not already existent. These scripts can be copied to this chrome folder and loaded at next browser start. They contain new functions or buttons to enhance functionality or usability of Mypal 68. Unfortunately, the compatibility of these userscripts *.uc.js depends on the targeted version of Firefox. Therefore, only a few of them will work natively in Mypal 68 unless you are able to modify them or write your own scripts. And there are some requirements to be fulfilled to get them working in Mypal 68. Requirements for loading UC.JS scripts and CSS stylesheets in Mypal 68 1. In the profile folder of Mypal 68 a new folder "chrome" and a subfolder "css" of folder chrome have to be created if not already existent. Now you should have the following structure in your profile folder: mypal_profile_folder\ mypal_profile_folder\chrome\ mypal_profile_folder\chrome\css\ 2. Five files have to be added to Mypal 68. Copy config.js to Mypal's installation folder, next to mypal.exe. Copy config-prefs.js to \defaults\pref inside Mypal installation folder, next to channel-prefs.js. Finally, save userChrome.js, userChrome.css and userChrome.xml into Mypal chrome folder. 3. The variable general.config.sandbox_enabled has to be set to false in about:config which should be done automatically by file config-prefs.js after restarting the browser. Two further variables will be set by this file: general.config.filename to string config.js and general.config.obscure_value to value 0. Another variable toolkit.legacyUserProfileCustomizations.stylesheets has to be set to true which should be done automatically by config.js. 4. Now, new custom button UC.JS scripts can be added to the profile's chrome folder. They all end with the extension .uc.js, for example RestartFirefoxButton_Movable.uc.js. In some cases, the userChrome.css file has to be edited to load additional CSS files needed by the already added UC.JS script files. In any case, all CSS stylesheets files have to be copied to the css subfolder from where they have to be always imported by the userChrome.css file via the import command or alternatively by a CSS loader script. This is the download link of the package MYPAL_68_CB_requirements.7z I created which contains all required files for the custom buttons and CSS implementations posted by me: https://www.mediafire.com/file/m84enyyuz7up01y/Mypal_68_CB_requirements.7z/file Update 14.01.2025 Custom Buttons requirements, i.e. the Nuchi-Sporif UC.JS script loader for Mypal 68 and compatible browsers. Modified and provided by AstroSkipper. 1. In the profile folder of Mypal 68 a new folder "chrome" and a subfolder "css" of folder chrome have to be created if not already existent. Now you should have the following structure in your profile folder: mypal_profile_folder\ mypal_profile_folder\chrome\ mypal_profile_folder\chrome\css\ 2. Five files have to be added to Mypal 68. Copy the config.js file into Mypal's installation folder, next to the main executable mypal.exe. Copy the config-prefs.js file to the defaults\pref subfolder inside the Mypal installation folder, next to the already existing channel-prefs.js file. Finally, copy the files userChrome.js, userChrome.css and userChrome.xml into the Mypal chrome folder. 3. For the Nuchi-Sporif script loading method, the preference general.config.filename will be automatically set to the string value of config.js by the config-prefs.js file after starting the browser. The preference general.config.sandbox_enabled can be left at Mypal's default for this method. Only for other script loading methods, it has to be set to the Boolean value of false in about:config, which means, it then should be enabled in the config-prefs.js file (since I have commented it out for the use of the Nuchi-Sporif script loading method at the moment) and automatically set by this file after starting the browser. The preference general.config.obscure_value doesn't seem to be absolutely necessary for the Nuchi-Sporif script loading method either, but for the legacy Custom Buttons extension and has to be set to the value of 0. This will be automatically done by the config-prefs.js file after starting the browser. Last but not least, another important preference toolkit.legacyUserProfileCustomizations.stylesheets has to be set to the Boolean value of true which will be automatically done by the config.js file. 4. Now, new custom button UC.JS scripts can be added to the profile's chrome folder. They all end with the extension .uc.js, for example RestartFirefoxButton_Movable.uc.js. In some cases, the userChrome.css file has to be edited to load additional CSS files needed by the already added UC.JS script files. In any case, all CSS stylesheets files have to be copied to the css subfolder from where they have to be always imported by the userChrome.css file via the import command or alternatively by a CSS loader script. Here is a short changelog of my new package Mypal 68 CB requirements - Updated 12.01.2025.7z: In the config-prefs.js file, comments added and the pref general.config.sandbox_enabled deactivated. In the config.js file, unnecessary code removed. In the userChrome.css file, information added how to import CSS stylesheets. In the userChrome.js file, the error "ReferenceError: XPCOMUtils is not defined" fixed in two different ways: either unnecessary code completely removed, or the corrected file userChrome.js.FixedJustForFunByAstroSkipper can be used (the extension .FixedJustForFunByAstroSkipper has to be removed, of course ). Instructions in the Instructions - Please read me first!.txt file updated. This is the download link of the package Mypal 68 CB requirements - Updated 12.01.2025.7z I created which contains all required files for the Nuchi-Sporif script loading method to load UC.JS scripts and CSS stylesheets in Mypal 68: https://www.mediafire.com/file/08g7r4brr5mukkh/Mypal_68_CB_requirements_-_Updated_12.01.2025.7z/file News about the Nuchi-Sporif script loading method - 23.04.2025 The Nuchi-Sporif script loading method I have made available in this post is only working up to Mypal 68.14.7b. With @feodor2's release Mypal 68.14.8b, this method completely stopped working. From now on, I recommend the Alice0775 script loading method from 4th place in my ranking list of all script loading methods which I had tested some months ago: Extensions in Mypal 68 As already mentioned, Mypal 68 supports only web extensions. We can try to use all web extensions which are provided on official Firefox Extensions homepage: https://addons.mozilla.org/en-US/firefox/extensions/. But do not think each of them will work in Mypal 68! First we have to take account of the minimum version number less or equal to 68, of course, but that's not all. A lot of supposedly compatible extensions don't work in Mypal 68. For example, many "Clear Cache" extensions don't do their job properly. You think the cache has been deleted by clicking, but that's a fallacy. Either you have to install some so-called "native applications" which have to be installed in your system to grant access to restricted functions in Mypal 68, unfortunately not being Windows XP compatible like, for example, node.js, a JavaScript runtime built, or they simply don't work as expected. The same applies to the so-called browser restart extensions. They are not able to perform a complete, real restart of Mypal 68. I found a lot of them, and they are all crap. Anyway, beware of these useless, crappy extensions! Update notification: 10/06/2022: The file MYPAL_68_CB_requirements.7z has been updated and corrected. Download link above. 11/06/2022: New beta version released: Mypal 68.12.4b. Download link: https://github.com/Feodor2/Mypal68/releases/download/68.12.4b/mypal-68.12.4.en-US.win32.zip 10/08/2022: New beta version released: Mypal 68.12.5b. Download link: https://github.com/Feodor2/Mypal68/releases/download/68.12.5b/mypal-68.12.5.en-US.win32.zip 14/05/2023: New beta version released: Mypal 68.13.0b. Download link: https://mega.nz/file/QaY1zLLY#PhGLpVBfu51To4sjqSgfjaLX6nyebwye82FliTf41yA 28/06/2023: New beta version released: Mypal 68.13.1b. Download link: https://github.com/Feodor2/Mypal68/releases/download/68.13.1b/mypal-68.13.1.en-US.win32.zip 15/07/2023: New beta version released: Mypal 68.13.2b. Download link: https://github.com/Feodor2/Mypal68/releases/download/68.13.2b/mypal-68.13.2.en-US.win32.zip 07/10/2023: New beta version released: Mypal 68.13.3b. Download link: https://github.com/Feodor2/Mypal68/releases/download/68.13.3b/mypal-68.13.3.en-US.win32.zip 17/10/2023: New beta version released: Mypal 68.13.4b. Download link: https://github.com/Feodor2/Mypal68/releases/download/68.13.4b/mypal-68.13.4.en-US.win32.zip 30/10/2023: New beta version released: Mypal 68.13.5b. Download link: https://github.com/Feodor2/Mypal68/releases/download/68.13.5b/mypal-68.13.5.en-US.win32.zip 11/11/2023: New beta version released: Mypal 68.13.6b. Download link: https://github.com/Feodor2/Mypal68/releases/tag/68.13.6b 18/11/2023: New beta version released: Mypal 68.13.7b. Download link: https://github.com/Feodor2/Mypal68/releases/tag/68.13.7b 07/01/2024: New beta SSE version released: Mypal 68.13.8b. Download link: https://github.com/Feodor2/Mypal68/releases/tag/68.13.8b 17/02/2024: New beta version released: Mypal 68.13.9b. Download link: https://codeberg.org/Theodor2/Mypal68/releases/tag/68.13.9b 24/04/2024: New beta version released: Mypal 68.14.0b. Download link: https://codeberg.org/Theodor2/Mypal68/releases/tag/68.14.0b 04/05/2024: New beta version released: Mypal 68.14.1b. Download link: https://codeberg.org/Theodor2/Mypal68/releases/tag/68.14.1b 01/06/2024: New beta version released: Mypal 68.14.2b. Download link: https://codeberg.org/Theodor2/Mypal68/releases/tag/68.14.2b 21/07/2024: New beta version + beta SSE version released: Mypal 68.14.3b. Download link: https://codeberg.org/Theodor2/Mypal68/releases/tag/68.14.3b 03/08/2024: New beta version + beta SSE version released: Mypal 68.14.4b. Download link: https://codeberg.org/Theodor2/Mypal68/releases/tag/68.14.4b 25/11/2024: New beta version version released: Mypal 68.14.5b. Download link: https://github.com/Feodor2/Mypal68/releases/tag/68.14.5b 14/01/2025: The file MYPAL_68_CB_requirements.7z has been updated and corrected and is now named Mypal 68 CB requirements - Updated 12.01.2025.7z. Download link above. 25/01/2025: New beta version + beta SSE version released: Mypal 68.14.6b. Download link: https://github.com/Feodor2/Mypal68/releases/tag/68.14.6b 01/02/2025: New beta version + beta SSE version released: Mypal 68.14.7b. Download link: https://github.com/Feodor2/Mypal68/releases/tag/68.14.7b 02/05/2025: New beta version + beta SSE version released: Mypal 68.14.8b. Download link: https://github.com/Feodor2/Mypal68/releases/tag/68.14.8b 14/07/2025: New beta version + beta SSE version released: Mypal 74.1.0. Download link: https://github.com/Feodor2/Mypal68/releases/tag/74.1.0 02/08/2025: New beta version + beta SSE version released: Mypal 74.1.1. Download link: https://github.com/Feodor2/Mypal68/releases/tag/74.1.1 In this thread, please post only useful custom buttons or extensions, tested and fully working in the most recent version of Mypal 68! If not, a note is necessary which version of Mypal is targeted. "Useful" means this custom button or extension should have a meaningful and real benefit for its user, contrary to just only working or looking nice. The post should include a headline with the name of the custom button or extension in bold and font size 18, a short description (one sentence including purpose and version number), some important remarks regarding to installation or usage, if necessary, and a download link, of course. All posted custom buttons, script-generated objects, CSS code implementations, extensions or special articles that meet these conditions will be listed alphabetically in the second or third post, with a link to the member's original comment for better overview. Due to the modular character of this thread, each posted custom button or extension can be upvoted or liked separately with credits to their poster. Any opinions, experiences, discussions, or questions about these custom buttons or extensions are explicitly welcome. But one thing must be totally clear, everything should relate to this topic. That means please stay on-topic! If you enjoyed this thread, or maybe you found it interesting and helpful, we would be pleased about any reaction by liking or upvoting and of course commenting. Kind regards, AstroSkipper

Good Day All, Mypal 68 series (currently through version 78.0.2), by @feodor2, has various UI elements that are hidden without a UI or setting option to unhide or un-obfuscate the UI elements. Presumably, this is how it normally is with Mozilla Firefox Quantum, for which Mypal 68 series is a derivative work. In (much) older versions of Firefox, these elements were not obfuscated or hidden, existing of the elements at issue permitting. I hereby present a userChrome.css Cascading Style Sheet document that I created to make the UI element behave or be available reasonably again (as they once were). I have had this style sheet for a while, but never posted it (I might have tried long ago but was having difficulty with posting troubles at the time). The style sheet works on Mypal 68.x series generally and is intended to work across normal themes and style densities. The CSS changes are generally made directly against the actions from the internal browser CSS. An issue to note, is that #urlbar-go-button used to be .urlbar-go-button in the internal browser CSS and thus my provided userChrome.css's content should so be so adjusted if it is to be used with old versions of Mypal 68 that use the older reference. I am uncertain (did not retain note) which browser version increment resulted in the change, but I believe it was a release during year 2024. The style corrects the following problems (Changes described in the parentheses): The Stop and Reload Buttons, in button container, are combined into one button space and only one button displays at a time and in a manner not select-able by the user. (The Stop and Reload Buttons now should remain in separate button spaces (are still both together in a button container)) The Go Button is often hidden. (The Go button is now always shown.) The Location Bar Dropdown marker is invisible despite being present. (The Location Bar Dropdown marker is made always visible.) The Searchbox's Go button is often hidden. (The Searchbox's Go is now always shown). Many Menubar menu items are hidden when something other than the keyboard (such as a mouse) is use to first open a Menubar menu. (Menubar items are now also displayed when something other than the keyboard (such as a mouse) is use to first open a Menubar menu). Location bar Dropdown marker and Location Bar Go button (and relative also to the Location Bar Page Action Buttons container) are postponed in places where they might not be static (stay in the same place) and are in different relative places than classical design (here, meaning pre-Quantum). (Item relative locations are adjusted so that to they are ordered in the classical layout (meaning pre-Quantum). As a side note and unfortunately, with regards to the Location bar items positioning, for post-Quantum Firefox, the Mozilla design choice becomes instead to remove these UI elements so they do not display and cannot be used. The userChrome.css CSS style sheet I provide is attached herewith and its content is the following: @namespace url("http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul"); /* set default namespace to XUL */ /* --Section START---------------- */ /* Separate Stop and Reload buttons (remains in its own container button) */ /* CSS cannot remove the encapulating container now present in Quantum */ #stop-button, #reload-button { display: -moz-box !important; } /* To suppress display of animation, Disable the filled stepping effect when button animating */ /* This is done to prevent the animations onto the stop or reload buttons that includes pictures of the other button */ /* This provides the classic-looking behavior for Firefox */ #stop-reload-button[animate] > #reload-button > .toolbarbutton-icon, #stop-reload-button[animate] > #reload-button[displaystop] + #stop-button > .toolbarbutton-icon { fill: none !important; } /* Must also disable the animation display */ #reload-button > .toolbarbutton-animatable-box, #stop-button) > .toolbarbutton-animatable-box { display: none !important; } /* Disable animation so things look right on dark and light (default) themes */ #reload-button:not([displaystop]) > .toolbarbutton-animatable-box > .toolbarbutton-animatable-image { animation-duration: 0ms !important; } #reload-button[displaystop] + #stop-button > .toolbarbutton-animatable-box > .toolbarbutton-animatable-image { animation-duration: 0ms !important; } /* Remove pictures used for animations (which include stop and reload pictures together for both stop and reload buttons) */ /* Important for dark theme to look okay if animation is allowed (duration). Otherwise, would look okay on normal theme */ /* I have disabled animations with code above, but including here anyways for completeness */ #stop-reload-button[animate] > #reload-button > .toolbarbutton-animatable-box > .toolbarbutton-animatable-image { background-image: none !important; } #stop-reload-button[animate] > #reload-button[displaystop] + #stop-button > .toolbarbutton-animatable-box > .toolbarbutton-animatable-image { background-image: none !important; } /* ------------------Section END-- */ /* #page-action-buttons is Container for set of buttons that includes the Star button, Page Actions button, pageActionSeparator (a simple separator button that does nothing more), and Reading View (and maybe others) */ /* Explicitly set ordinal group to be before the explicitly set URLbar History Dropdown marker button and Go button */ /* Likley unnecessay in default theme, but perhaps good where order is different for other reason (such as another theme) */ #page-action-buttons { -moz-box-ordinal-group: 97 !important; } /* Always display Location Bar "Go" button, and on the extememost postion (end of URLbar) */ /* Unhides the URLbar Go button and always display the button AND positions it at end of URLbar */ #urlbar-go-button { -moz-box-ordinal-group: 99 !important; display: -moz-box !important; } /* Always display Location Bar Dropdown marker and position at end directly before postion of urlbar-go-button */ .urlbar-history-dropmarker { -moz-box-ordinal-group: 98 !important; display: -moz-box !important; /* Needed to override the hiding when typing */ opacity: 1 !important; /* By default when closed, marker is made transparent; this removes the transparency */ } /* Unhide Searchbox Go button */ .search-go-button { display: -moz-box !important; } /* Unhides extra hidden menu items if keyboard is not used to access the menu that contains them */ /* Exempting menu items that should remain hidden */ #main-menubar .show-only-for-keyboard:not([hidden="true"]) { display: -moz-box !important; } To use the CSS styles here provided, place the userChrome.css style sheet file in the browser user profile directory's "chrome" subdirectory. If a userChrome.css file pre-exisists there, decide how to incorporate the changes I present in this style sheet, with the existing file, or optionally, replace the file (which may overwrite and prevent new usage of the previously installed userChrome.css file.) A picture of the browser after my userChrome.css file is applied: [Could not post here. Forum wants smaller picture size, despite already being small.] Linking from image hosting site: Enjoy. userChrome.css

I finally managed to get Serpent/Mypal 68 to work on Windows XP SP1 (and also SP2). Notes kernelxp.dll stays in the "mypal" and "basilisk" directories after patching, or else it will NOT work. mypal68-xpsp1-code.txt serpent-xpsp1-code.txt

Autorun LWMenu https://www.portablefreeware.com/index.php?id=2887, see discussion on usage at https://www.portablefreeware.com/forums/viewtopic.php?t=20583 WinpernPac'''s X-Launcher updated *have not tried it yet) https://www.portablefreeware.com/forums/viewtopic.php?p=107107#p107107