Jump to content

AstroSkipper

Member
 View Profile  See their activity

  • Posts

    4,565

  • Joined

  • Days Won

    463

  • Donations

    0.00 USD 

  • Country

    Germany

 Content Type 

Everything posted by AstroSkipper

  1. AstroSkipper
    I know you are a fan of Violentmonkey. I use it in Serpent, too (thanks to your hint what needed to be fixed in version 2.14.0 ). But in Mypal 68, I use Tampermonkey. Do you see any advantages in using Violentmonkey instead of Tampermonkey? Maybe, in terms of script compatibility? Or is it just a personal preference in the end?
  2. AstroSkipper
    That makes sense, of course. I checked it by using a fresh profile in NM 28 where no changes have been done by me. Therefore, I used logically the standard UA.
  3. AstroSkipper
    In New Moon 28, using a fresh profile, and logged into a Google account or not, this Google search setting is not available. It looks and behaves like the old search. You get your search results page by page after clicking as it was before.
  4. AstroSkipper
    In Mypal 68, it persists, too. BTW, no cookie protection here.
  5. AstroSkipper
    mozlz4-edit The extension mozlz4-edit lets you edit and/or add custom search engines to Mypal 68 without using an internet connection. Actually, mozlz4-edit is a simple mozlz4 file editor. You can open, edit and save mozlz4 files. Tested version: 4.1.2 How to 1. Find the search.json.mozlz4 file inside of your Mypal 68 profile folder. 2. Backup the search.json.mozlz4 file first. 2. Open the search.json.mozlz4 file with the mozlz4-edit extension. 3. Edit and/or add a custom search engine entry. 4. Save the modified search.json.mozlz4 file in your Mypal 68 profile folder. 5. Restart Mypal 68. Here is a screenshot: Warning! You should not delete default search engines from a search.json.mozlz4 file if you edit the file. If you delete a default search engine, then the Firefox will reset search engine list to a default state. But you can add new search engines. Download link: https://addons.mozilla.org/de/firefox/addon/mozlz4-edit/ The extension mozlz4-edit is the other one of those I mentioned in my post about Managing search engines in Mypal 68. I tested this extension by editing a custom search engine and adding it to Mypal 68. It also worked without any problems.
  6. AstroSkipper
    Update notification! As already reported here, the Root Certificates have been updated and are now from 28-11-2023. Here is a screenshot: Therefore, my self-created, offline Root Certificate Updaters in the section 11.2.4. Downloads related to Root Certificate Updates (in the first post of this thread) will also be updated as soon as possible. Cheers, AstroSkipper
  7. AstroSkipper
    I updated my lists in the second and fourth post of this thread. Then I downloaded the most recent Avast VPS update for versions 9 to 11 which can be found here: https://install.avcdn.net/ivps9x/vpsupd.exe I compared this file to the one from 16.10.2023, and both are identical. Since the middle of October, the Avast VPS offline updater for versions 9 to 11 wasn't renewed anymore. Thus, I have to say: Avast 2015, rest in peace!
  8. AstroSkipper
    Hello @Dušan Vićić! As you can see, I already wrote about that. And now, as the end of this summer happened weeks or months ago, Avast stopped delivering definition updates on versions 9/10/11 since November 2023. Thus, I will update my lists in the first posts. Thanks for your reminder!
  9. 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.
  10. AstroSkipper
    Thanks for the information! Then the chances are quite good that after @feodor2's switch to JS Engine 91, some things will work again.
  11. AstroSkipper
    @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.
  12. AstroSkipper
    @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
  13. 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
  14. 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.
  15. AstroSkipper
    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.
  16. AstroSkipper
    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.
  17. AstroSkipper
    @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
  18. 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
  19. 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.
  20. AstroSkipper
    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!
  21. AstroSkipper
    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.
  22. AstroSkipper
    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
  23. 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
  24. 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!
  25. 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.
×
×
  • Create New...