Jump to content

AstroSkipper

Member
 View Profile  See their activity

  • Posts

    4,859

  • Joined

  • Days Won

    644

  • Donations

    0.00 USD 

  • Country

    Germany

 Content Type 

Everything posted by AstroSkipper

  1. AstroSkipper
    As far as I know, Serpent 52 gets more patches from the UXP branch than Serpent 55. The reason for that is not all of these patches can be applied to Serpent 55. Therefore, Serpent 52 is a bit more up-to-date. But @roytam1 and @VistaLover can tell more about that. And if I remember correctly, they already did that in @roytam1's browser threads in the past.
  2. AstroSkipper
    No, I do not use the property window.status. The script code for creating such a status bar has not grown out of my own hands, though. I simply took over an old script which is still working in Mypal 68. TBH, there are a couple of scripts but most of them are not compatible with Mypal 68. My part was finding working code. And that wasn't so easy due to the age of Firefox 68. Many scripts targeting this Firefox version have been lost or replaced by newer ones. However, I modified the css file for exact placing the status panel onto the status bar by myself. And the css file I am using is much more modified and exactly adapted to my browser, in which I also made changes to the interface font. This file is therefore useless for other users.
  3. AstroSkipper
    Update notification! FYI, I have just updated my articles in the first, second and third post of this thread. Cheers, AstroSkipper
  4. AstroSkipper
    Not only does it seem that way, but I have definitely implemented a toolbar as a status bar in Mypal 68 with the functionality to display currently loading URLs and hovered links and to place toolbar buttons there as you can see in my previously posted pictures. To achieve this, only two files are required, a JavaScript uc.js file in the chrome profile folder and a corresponding Cascading Style Sheet css file in the chrome/css subfolder. The css file must then of course be integrated into the userchrome.css file. The prerequisite for all this is, of course, the preparations that must be made once in order to be able to load scripts and css files from the chrome folder into Mypal 68 as described by me in the first post of this thread. So, I do not use a startup auto-configuration script. You only need, for example, my package MYPAL_68_CB_requirements.7z from the first post. And to implement an additional toolbar near the navigation bar for placing buttons, you only need one other JavaScript uc.js file. In general, the implemetation of a new toolbar can only be done by a JavaScript uc.js file and any styling of it if necessary or desired by a css file. Such changes of the browser interface cannot be done by webextensions due to their damn restrictions. I actually wanted to write an article about all of this long ago, but refrained from doing so due to a lack of interest. Logically, disinterest and passivity are not particularly motivating. Anyway! When I am back at my desktop computer, I can give you more information if you are still interested in. Cheers, AstroSkipper
  5. AstroSkipper
    Another nice variant, fully working in Serpent 52, is the extension What about:.. 4.15 which can be also downloaded from the Classic Add-ons Archive.
  6. AstroSkipper
    The obvious always speaks for itself. Things that are such self-explanatory and clear do not need any longer to be explained in detail. Apart from that, a more in-depth consideration would be inadmissible due to our forum rules and of no use in certain cases anyway.
  7. AstroSkipper
    This extension also no longer works in Serpent 52. Just tested.
  8. AstroSkipper
    If you don't want such tons of toolbar buttons (I personally love this extension ), then the extension More About 3.0.0 is a good alternative. You can get it via the Classic Add-ons Archive.
  9. AstroSkipper
    @dmiranda The easiest and most convenient way to add such an About Menu button to Serpent 52 is to use the Toolbar Buttons 1.1.1 extension. This extension comes with many toolbar buttons or rather tons of them. Although this extension is old, most of the toolbar buttons still work in @roytam1's browsers. One of them is the button about:about which is still working in Serpent 52. Here are two screenshots. You can download the extension Toolbar Buttons 1.1.1 via the Classic Add-ons Archive. I will write an article about this extension very soon. BTW, I already wrote about Toolbar Buttons 1.1.1 and the about:about button here: https://msfn.org/board/topic/182647-my-browser-builds-part-3/?do=findComment&comment=1225677 Greetings, AstroSkipper
  10. AstroSkipper
    Actually, the About: Menu custom button should work in Serpent 52, too. When I am back at my desktop computer, I will have a look at this. In New Moon 28, however, I can definitely confirm that this custom button works as it should. Generally, most custom buttons tested by me should work in both browsers. But, of course, we all know the proof is in the pudding. I have just tested it and have unfortunately to confirm your observation. Although there is the compatibility string of Firefox {ec8030f7-c20a-464f-9b0e-13a3a9e97384} inside the code of the About: Menu custom button, the menu of all about: pages does not open in Serpent 52. The button was created many years ago, though. Therefore, it definitely was developed for much older Firefox versions (< 52). That's presumably why it is still working in New Moon 28. But there are still alternatives in the form of extensions for Serpent 52 which can be tested. I will have a look at that later.
  11. AstroSkipper
    In my very old New Moon profile, I have 67 extensions enabled and 5 disabled. But in the more recent profiles, I try to use much less of them.
  12. AstroSkipper
    Actually, I thought the About: Menu custom button would work in Serpent 52, too. When I am back at my desktop computer, I will have a look at this. In New Moon 28, however, I can definitely confirm that this custom button works as it should. Generally, most custom buttons tested by me worked in both browsers. But, of course, we all know the proof is in the pudding.
  13. AstroSkipper
    As I already explained, I try to use as few extensions as possible, as they have a greater impact on memory and tend to cause compatibility problems. If features can be retrofitted by custom buttons, I use them instead of extensions. But I have to admit that I still install far too many extensions, but of course I also use them. As everyone knows by now, I'm also a big fan of extensions. The About: Menu custom button was created by the well-known developer LouCypher long ago. I just modded it a bit as described in my article.
  14. AstroSkipper
    Personally, I do not use any Yandex websites or services due to well-known reasons.
  15. AstroSkipper
    Yes. All about @roytam1's browser editions can be read here in this thread. And we had recently discussions about their diferences. Simply perform a search in this thread! In any case, New Moon 28 and Serpent 52 are UXP browsers.
  16. AstroSkipper
    Apparently, you have not understood my quotes and the conclusion to be drawn from them. Your statement does not correspond to the facts. With the release of NM28XP build 20240406, there were indeed changes, however, all coming from the the UXP platform.
  17. AstroSkipper
    About: Menu - A custom button for accessing all about: pages via a toolbar menu The About: Menu custom button, created by the well-known developer LouCypher long time ago, is another useful one. It gives the user the opportunity to access any desired about: page by clicking onto the corresponding entry inside a toolbar button menu. This menu contains all entries which are listed on the about:about page, but it is more convenient to access via a toolbar button. Here is a screenshot: I only changed the tool tip text and replaced the image of the toolbar button icon by the one from the Add-ons Manager. I should mention at this point that the button does not work in Serpent 52, but in New Moon 28. Thanks to @dmiranda for reporting! I uploaded the About: Menu custom button as an HTML file for an offline installation. Here is the download link of my modded custom button About: Menu, credits, of course, to its great developer LouCypher: https://www.mediafire.com/file/o931jc1a3e7l9zj/About-_Menu_4-7-24__021410.htm/file Simply open this HTML file in a browser tab and click the embedded custom button link for About: Menu! For the installation of this button, as for all others too, the extension Custom Buttons is required and has to be installed first. You can get it from this post: https://msfn.org/board/topic/183923-extensions-and-custom-buttons-for-uxp-browsers-corrections-modifications-adjustments-and-special-recommendations/?do=findComment&comment=1226328 Greetings from Germany, AstroSkipper
  18. AstroSkipper
    Right! "No official Pale-Moon changes picked since my last build", but "Official UXP changes picked since my last build".
  19. AstroSkipper
    And since I've talked so much about custom buttons recently, I'll introduce another one next, so that you don't get the impression that this guy here is just babbling.
  20. AstroSkipper
    Personally, I have no problem with something no longer working. But if it also produces error (messages), then it's a completely different story. Get rid of it!
  21. AstroSkipper
    Me, too. When I had fixed all errors in my Windows XP system years ago, I also removed this Microsoft Auto Certificates Updater component. And bye, bye error messsges in the Event Viewer.
  22. AstroSkipper
    If I post custom buttons here, regardless of whether they were created by me or by someone else, or in some cases, modded or fixed by me, then this results in a clear advantage for the user. These custom buttons have definitely been tested by me and are compatible with the Custom Buttons extension and @roytam1's UXP browsers. And most probably compatible with Basilisk and Pale Moon, too. Isn't that a great service?
  23. AstroSkipper
    Creating this thread was complex and very time-consuming. Right from the start, I paid attention to a good and clear structure. In the first three posts of this thread, I made a clear differentiation between extensions and custom buttons: Introductory post: https://msfn.org/board/topic/183923-extensions-and-custom-buttons-for-uxp-browsers-corrections-modifications-adjustments-and-special-recommendations/?do=findComment&comment=1226243 Extensions: https://msfn.org/board/topic/183923-extensions-and-custom-buttons-for-uxp-browsers-corrections-modifications-adjustments-and-special-recommendations/?do=findComment&comment=1226244 Custom buttons and other articles: https://msfn.org/board/topic/183923-extensions-and-custom-buttons-for-uxp-browsers-corrections-modifications-adjustments-and-special-recommendations/?do=findComment&comment=1226245 All listed entries there have been linked to their corresponding posts. Thus, all is easy to find. In my opinion, that will have to suffice. BTW, such kind of structure is rather rare to find here in this or other forums (actually fora), if I may say so. But thanks for your opinion!
  24. AstroSkipper
    There are actually a lot of extensions or custom buttons that are just waiting to be given a new lease of life. Therefore, I would also very much welcome it if more users of UXP browsers who have the appropriate skills would fork and develop extensions or custom buttons. Strictly following the rule: the more, the better.
  25. AstroSkipper
    TBH, I have known all this for a long time. That's why I listed all these sources in my first post in this thread. BTW, I have forked extensions too and made some fully working again. Not only uBlock Origin Legacy but also, for example, Check My IP Address & Location. But what I am trying to do at the moment is to get back the user's focus on custom buttons which are really great and deserve it.
×
×
  • Create New...