AstroSkipper

Editing and changing the order of the about items is very easy, BTW, some items don't work in Mypal 68. Thus, I deleted them months ago.

Thanks for the information! Then the chances are quite good that after @feodor2's switch to JS Engine 91, some things will work again.

@feodor2 The website https://www.camp-firefox.de/ works no longer correctly in Mypal 68 for a few days. Especially the site search function https://www.camp-firefox.de/suche/ is broken. Here is the output of the Web Console: SyntaxError: private fields are not currently supported WebComponent.min.js:58:1408 ReferenceError: WoltLabLanguage is not defined de.preload.js:2:1 SyntaxError: private fields are not currently supported WoltLabSuite.Core.tiny.min.js:1:33256 ReferenceError: requirejs is not defined suche:49:1 ReferenceError: define is not defined WoltLabSuite.Forum.tiny.min.js:1:1 ReferenceError: require is not defined suche:531:2 ReferenceError: define is not defined suche:561:2 ReferenceError: define is not defined suche:566:2 ReferenceError: require is not defined suche:607:3 ReferenceError: require is not defined suche:612:2 jQuery.Deferred exception: SECURITY_TOKEN is not defined init@https://www.camp-firefox.de/js/WCF.Combined.tiny.min.js?v=1701002591:19:8603 i@https://www.camp-firefox.de/js/WCF.Combined.tiny.min.js?v=1701002591:16:191 init@https://www.camp-firefox.de/js/WCF.Combined.tiny.min.js?v=1701002591:43:226 @https://www.camp-firefox.de/suche/:577:38 f@https://www.camp-firefox.de/js/WCF.Combined.tiny.min.js?v=1701002591:4:38929 o/</p<@https://www.camp-firefox.de/js/WCF.Combined.tiny.min.js?v=1701002591:4:39232 undefined WCF.Combined.tiny.min.js:4:40512 jQuery.Deferred exception: require is not defined addObject@https://www.camp-firefox.de/js/WCF.Combined.tiny.min.js?v=1701002591:19:13911 @https://www.camp-firefox.de/suche/:592:17 f@https://www.camp-firefox.de/js/WCF.Combined.tiny.min.js?v=1701002591:4:38929 o/</p<@https://www.camp-firefox.de/js/WCF.Combined.tiny.min.js?v=1701002591:4:39232 undefined WCF.Combined.tiny.min.js:4:40512 ReferenceError: SECURITY_TOKEN is not defined WCF.Combined.tiny.min.js:19:8603 ReferenceError: require is not defined WCF.Combined.tiny.min.js:19:13911 This site appears to use a scroll-linked positioning effect. This may not work well with asynchronous panning; see https://developer.mozilla.org/docs/Mozilla/Performance/ScrollLinkedEffects for further details and to join the discussion on related tools and features! suche There is a lot not defined. Have a look above! The admins of this websites must have recently performed changes. In New Moon 28 and Serpent 52, the site search surprisingly works.

@dmiranda The solution to let the custom button aboutbutton recognise by the CSS stylesheet buttons_on_navbar_button_roundness.css is a bit more complicated than I thought. You have indeed to change the code of the script aboutbutton.uc.js. It seems to be a class issue. This is the first part of the original script code from line 1 to 26: (function() { if (location != 'chrome://browser/content/browser.xul') return; try { CustomizableUI.createWidget({ id: 'about-toolbarbutton', type: 'custom', defaultArea: CustomizableUI.AREA_NAVBAR, onBuild: function(aDocument) { var toolbaritem = aDocument.createElementNS('http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul', 'toolbarbutton'); var attrs = { id: 'about-toolbarbutton', class: 'chromeclass-toolbar-additional', type: 'menu', removable: true, label: 'about Seiten öffnen', tooltiptext: 'about Seiten öffnen' }; for (var a in attrs) toolbaritem.setAttribute(a, attrs[a]); return toolbaritem; } }); } catch(e) { }; I changed the class of this button in line 15 from 'chromeclass-toolbar-additional' to 'toolbarbutton-1 chromeclass-toolbar-additional': (function() { if (location != 'chrome://browser/content/browser.xul') return; try { CustomizableUI.createWidget({ id: 'about-toolbarbutton', type: 'custom', defaultArea: CustomizableUI.AREA_NAVBAR, onBuild: function(aDocument) { var toolbaritem = aDocument.createElementNS('http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul', 'toolbarbutton'); var attrs = { id: 'about-toolbarbutton', class: 'toolbarbutton-1 chromeclass-toolbar-additional', type: 'menu', removable: true, label: 'about Seiten öffnen', tooltiptext: 'about Seiten öffnen' }; for (var a in attrs) toolbaritem.setAttribute(a, attrs[a]); return toolbaritem; } }); } catch(e) { }; This change seems to be enough to let the CSS stylesheet buttons_on_navbar_button_roundness.css recognise the custom button aboutbuttuon as a standard toolbar button. Thus, the button can be rounded by this CSS stylesheet. Here is a screenshot to show the result of my change (I added borders around the buttons via CSS code for better visibility ): The positive side effect of this modification is that the custom button aboutbuttuon behaves as a normal toolbar button from now on, even if it is not rounded off by such a CSS stylesheet. Cheers, AstroSkipper

The aboutbuttuon is a special custom button coded quite unusually. It is generated in JavaScript by the var variable and is a menu button. When hovering on all buttons, you will notice that this button renders differenly from all the others. I think the code imported by the stylesheet buttons_on_navbar_button_roundness.css can't target this kind of custom button. It is simply not recognised as a standard toolbar button by the stylesheet. To change the appearance of this button in a toolbar (e.g. nav-bar) itself, you have to change the code inside the aboutbutton.uc.js file directly. Cheers, AstroSkipper

FYI, this also works on old browsers such as New Moon or Serpent. Never had a problem to tag a member in these browsers.

Thanks for the information! I personally have never heard of it before. I found a review on MalwareTips Forums which is from 2022 and unfortunately not positive. The author does not recommend this security programme. Here is a link: https://malwaretips.com/threads/huorong-internet-security-2022.119308/ But one review is of course not the world.

You're welcome! Glad it is working for you as it should. If you want to change to a light theme one day, you have of course to reinstall the original version of User Agent Status then. The modded version is only for dark themes.

@Mathwiz You can change the background and text colour as you prefer. The text can also be formatted in bold type. Here is another screenshot with bold text in the status bar panel: And here is the code: #ua-status-toggle {width: 24px; height: 24px;} toolbar[iconsize="small"] #ua-status-toggle {width: 16px; height: 16px;} #ua-status-main, #ua-status-label, #ua-status-main-input, #ua-status-button-setua, #ua-status-button-resetua { background-color: black !important; color: yellow !important; font-weight: 700 !important;} Just edit the overlay.css file to your liking exactly where I added the code! Greetings from Germany, AstroSkipper

Right! The overlay.css file inside the folder /chrome/skin is the one you have to modify. I have installed the theme FT DeepDark 14.3 theme and the extension User Agent Status 1.7.2 in Serpent 52. No problems here. The text in the status bar panel is readable. Here is a screenshot: At next, I added a bit CSS code to change the appearance of the status panel. I decided to keep the background colour which is obviously black and changed the text colour to yellow for better visibility. Here is a screenshot: Here is the download link to the modded version I made for you just for fun: https://www.mediafire.com/file/v4wa5byn6vgzeu4/ua-status-1.7.2-FT-DeepDark-mod.xpi/file Cheers, AstroSkipper

You're welcome! As I already mentioned, the most recent versions of CustomCSSforFx will contain CSS code targeting the much more recent Firefox versions. That's why I pick only single CSS stylesheets, test them in terms of compatibility and implement them if needed or wanted. The time range for picking them is from July 2019 to August 2020 as I already wrote in a previous post. Maybe, some of the CSS files from more recent CustomCSSforFx versions will also work in Mypal 68 but surely less than in the versions that have been specially adapted for Firefox 68. Apart from that, I prefer those CSS stylesheets that do not contain unnecessary code for versions of Firefox 69 and higher.

I don't use dark themes. Thus, it is working perfectly for me. But one thing is clear. You can change or modify extensions in every conceivable way, especially the legacy extensions for our beloved UXP browsers. I assume there is CSS code inside the extension which might be adapted for dark themes. Unpack the extension and have a look inside!

Hello @dmiranda! aboutbutton.uc.js is a JavaScript script file and does not need an entry in the userContent.css file. It has only to be copied to the chrome folder and will be recognized automatically after clearing the startup cache and restarting Mypal 68, only if all has been configured correctly (see first post of this thread), of course. It comes originally with an additional aboutbutton.css file to change the appearance of the button and its menu which has to be copied to the chrome\CSS subfolder and imported into the userChrome.css file. However, I had to fix this aboutbutton.css file as it didn't work correctly in Mypal 68. Anyway! The userContent.css file is for changing directly websites or internal sites like the about:sites. But for the custom button aboutbutton, no entries are necessary in the userContent.css file.

The stylesheets are not intended to be installed completely. You choose what you want to change and what you like. I only use a very few of them. Custom CSS stylesheets must be permanently adapted to new Firefox versions. Stylesheets that worked in a previous version do not necessarily have to work in the subsequent version. Mypal 68 is based on Firefox 68.12.0esr from August 2020. The regular Firefox 68 version (not esr) was released in July 2019. Thus, you have to look mainly for custom CSS stylesheets published from July 2019 to August 2020. Search for tabs_below_navigation_toolbar_fx68.css which depends on tabs_below_navigation_toolbar_fx65.css which in turn depends on tabs_below_navigation_toolbar.css! That means you have to copy all three files into your profile subfolder chrome\CSS and import the tabs_below_navigation_toolbar_fx68.css file only in your userChrome.css file via the following command: @import "./css/tabs_below_navigation_toolbar_fx68.css"; The good is that once you found working stylesheets they will work in Mypal 68 probably forever. Is mostly finished. It is not for public as I have not changed the name from Firefox to Mypal. Replace the string Firefox by the string Mypal in all files using the "replace all"-function of an editor as, for example, Notepad++! This is very easy and can be done in minutes. In any case, your compatriots would surely appreciate a working German language pack for Mypal 68.13.x. Cheers, AstroSkipper

Use custom CSS stylesheets from CustomCSSforFx to move the tab bar below the navigation and bookmarks bar! Look at my pictures, and you will see the distances fit perfectly. The custom CSS stylesheet I am using is originally from CustomCSSforFx but it has been modified by me and can't be directly used elsewhere due to special variables and changes. Thus, I won't provide it. But the original CSS stylesheet of course works as it is. And if you don't like a separate search bar, you can move the search function to the address bar. This can even be done natively in Mypal 68's settings, or you change more by using a script or another custom CSS stylesheet. BTW, didn't you actually want to create a German language pack for Mypal 68.13.x? Already published? Cheers, AstroSkipper

Glad you like it! Toggle CSP is one of my self-created custom buttons. Thanks for your patch! How do I have to apply it? I am not a Git user and not familiar with it. As far as I can see, it is a diff code. - means code to be removed and + means code to be added. Right? I assume it is targeting the modified config.js file where the original code was usually injected by the user, right? What is the final effect of this code change? Don't forget I am just a hobby coder! My strenghts are batch programming, CSS, a bit JavasScript and modifying/recycling existing code only if I understand the code and its problem. All is done locally on my computer. @feodor2 Ok! I tried myself. I removed the code marked with - and added the code marked with +, both simply manually. Works great! The Custom Buttons extension seems to be fully functional, and extensions which couldn't be installed before due to the message "Installation aborted because the add-on appears to be corrupt" can now be installed without any warnings. Is that what the code change is supposed to achieve? In any case, I will test this new code more deeply the next days, but first of all, a big thanks!

Glad you like it! Toggle CSP is one of my self-created custom buttons. Thanks for your patch! How do I have to apply it? I am not a Git user and not familiar with it. As far as I can see, it is a diff code. - means code to be removed and + means code to be added. Right? I assume it is targeting the modified config.js file where the original code was usually injected by the user, right? What is the final effect of this code change? Don't forget I am just a hobby coder! My strenghts are batch programming, CSS, a bit JavasScript and modifying/recycling existing code only if I understand the code and its problem. All is done locally on my computer.

I already posted the meaning of the error code 0x800706B5: Check if there are problems in your system with the event log service! @WSC4 As far as I understand your error code, the service BITS fails to start because the Eventlog service is not running. Check both services! Are they set to start automatically (auto)? BITS is definitely needed for MU/WU and has to be working correctly. And keep in mind, my guide was generally written for Windows XP Professional SP3 32-bit. But there were members like, for example, @maile3241 who got MU/WU running under Windows XP 64-bit using ProxHTTPSProxyMII 1.3a in the past. Whether it is still working in these days or not, I really don't know. If you can't fix it and all fails, you should give another method a try.

At the moment, I can't find the original link to the most recent version of Custom Buttons which I am currently using. Therefore, I'll upload it and send you the download link via PM.

It is not only a warning message which is shown in my images and when installing other unsigned extensions. The extension Custom Buttons, for example, is natively unsigned and does not work correctly due to the signature verification which seems to restrict its functionality. Only the hack did the trick which leads me to the conclusion that this feature has not really been removed, unfortunately. TBH, I hate all these restrictions in general. That's why I love the legacy UXP browsers. No serious restrictions. But nevertheless, Mypal 68 is a really good browser, and I appreciate your efforts.

I agree. I do not agree. You are a poster here in this thread like me, no more, no less. You can ask whatever you want but asking does not mean it is an order and everyone has to obey. If you don't want to reply to a post for whatever reason, it's your decision. You are free to do what you think. But same applies to me, too, of course. And once again, posting images for documenting purpose is no spamming, and it doesn't matter whether you like it or not. This thread is about the subject matter and not about sensitivities. Period. Now, back on topic, take any extension, remove the META-INF folder, and you've got an unsigned extension. Try to install it, and you will see what happens.

@feodor2 My posts are always rich in words, precise explanations, documented by images if necessary, on topic and written in the best possible English. You are the developer of Mypal 68 and for that you deserve recognition, but in this thread, you are a poster like any other. So please, act like it! Here, we are not in your issues on GitHub, where you have a lot of spammers and insulters, unfortunately. That's the reason why I stopped reporting issues there a few weeks ago, BTW.

What are you talking about? I ask you a simple question. And to be crystal clear, posting images for documenting facts is no spamming. You should know that regardless of your personal preferences. Everyone is different. Anyway! Based on the nature of your reply, I'll have to assume that your statement about removing the signature verification is indeed incorrect.

@feodor2 Thanks for the new release! In the release notes of Mypal 68.13.7b, you wrote: Unfortunately, I cannot confirm your statement in bold. The signature verification is still active in version 68.13.7b, and certain, unverified extensions do not work properly after installation. Here are two screenshots showing the installation of an unsigned extension: So, are you really sure that signature checking stuff has been removed? In any case, I cannot confirm this statement. AstroSkipper

@a8s If you're going to use a hack like this, you should also read the notes. Here is a quotation taken from the creator's notes: And if you had carried out a new installation straight away from scratch, as I advised you to do in this post, you would have immediately realised that the error was in your configuration.