Jump to content

AstroSkipper

Member
  • Posts

    4,565
  • Joined

  • Days Won

    460
  • Donations

    0.00 USD 
  • Country

    Germany

Everything posted by AstroSkipper

  1. In general, it's always a good idea not to make too many changes at once when it comes to software development. You don't want to end up like Mozilla, which breaks compatibility almost with every release. @feodor2 Here is my wish for Christmas: Please, recheck your changes and revert those which break compatibility! None of your previous releases caused any breakages to UC.JS scripts, CSS stylesheets, extensions or custom buttons. There was only one breakage in terms of language packs in the past. But all other things worked in every of your releases. Do not follow Mozilla's way of destruction!
  2. After all my tests and changes I made with UC.JS scripts, CSS stylesheets, custom buttons and extensions, the best and most stable version for me is Mypal 68.14.4b.
  3. 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.
  4. The Custom Buttons extension worked fine in Mypal 68 from the very first release until the previous version 68.14.4b. @feodor2 also has this extension available and can certainly test what's going on. In any case, he has made significant changes. The menu bar is also affected and no longer behaves as it did before. This may also be one of the reasons why some of my CSS stylesheets no longer work. Same applies to the Add-ons Manager. P.S.: @feodor2 And FYI, I also tried xiaoxiaoflood's method you recently pointed to and installed the boostrapped version of Custom Buttons (this extension always comes in two different versions). In this case, the extension options appears again in the Add-ons Manager (no error in the Browser Console in terms of the boostrap.js file) but when installing custom buttons, none of them are available. Although they are listed under the entry Custom Buttons in the Add-ons Manager, they are simply not accessible and their tool bar icons missing in the Customize window. Same to the Custom Buttons menu in the main toolbar. As you may know, Custom Buttons is an extension that also runs in newer Firefox versions up to the very latest. BTW, all was tested by me in a clean, fresh profile. If you need all the no longer working stuff, please let me know. I will then upload it for you. P.S.2: Furthermore, new errors can be found in the Browser Console compared with your previous release, even when opening the about:preferences page. Since you haven't been around here since 27. October, and the bugs are plentiful and serious, I even jumped over my shadow and reported it to your issues on GitHub to make sure you were aware of the problems with your new release.
  5. Hi @feodor2! Thanks for your new release and all your efforts to improve Mypal 68! Unfortunately, I have to report that my beloved Custom Buttons extension is no longer working due to the changes you made in Mypal 68.14.5b. Furthermore, some UC.JS scripts have stopped working. Same applies to some CSS stylesheets. All of them have been working fine in Mypal 68.14.4b but in your new release, they do not work anymore. Although the Custom Buttons extension can be installed, the extension options is missing and when installing some custom buttons, they do not appear. Neither they are listed under the entry Custom Buttons in the Add-ons Manager nor their tool bar icons are shown in the Customize window. The CB menu in the toolbar to create buttons is also missing. The Browser Console shows errors when reading the boostrap.js file of this extension. Try it yourself as you already have the Custom Buttons extension! At the moment, I will stay with Mypal 68.14.4b. Too much is not working in Mypal 68.14.5b.
  6. 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.
  7. 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.
  8. 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:
  9. 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.
  10. 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?
  11. 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.
  12. 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.
  13. 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
  14. When the CSS code for animations and transitions is active, you can't close some popups on MSFN. For example, the popup to see your recent notifications.
  15. Today, I have found a way to toggle all my CSS stylesheets in the chrome folder without restarting the browser by a mighty user script. So, no need anymore to use the Disable Transitions extension. From now on, I'll toggle all my CSS files via this script.
  16. I assume you found the CSS code here: https://superuser.com/questions/1224596/disable-css-animations-on-firefox If injected via userContent.css without any modifications which means using the CSS code globally, i.e. for all websites, it indeed works even with the "initial" CSS keyword. However, I had tested the code only on ebay.de by using @-moz-document url or @-moz-document domain, and this didn't work for me. In Mypal 68, I installed the extension Disable Transitions created by the author of the CSS code you found. Works absolutely great. To only use this code on eBay websites, enabling and disabling the extension is now my strategy, since this CSS code has negative effects on other sites as for example MSFN. In New Moon 28, I use the Stylem extensions to apply the CSS code. Even in this browser, I can successfully apply the code only globally and not locally. But with Stylem, you can quickly switch stylesheets on and off. So, problem solved for now.
  17. In the case of New Moon 28, you are right, but Mypal 68 and Thorium have not been updated since the bookmark was saved. By the way, in the CSS code you previously posted as a fix, only the "initial" keyword is present. The "initial" CSS keyword applies the initial (or default) value of a property to an element. Nothing more. To stop animations or transitions, there is actually the need of the "none" CSS keyword.
  18. Long story short. eBay websites (at least here in Germany) which worked fine some weeks or months ago must have recently changed, and their new layout is not pleasing. The page I quoted runs on my computer at 100% CPU utilisation in New Moon 28, Mypal 68 and even in Thorium. A short time ago, it was almost 0% after loading completely. That's a fact. I opened the same link I bookmarked weeks ago.
  19. Unable to replicate. ebayimg.map doesn't show up in any of my logs even when visiting https://www.ebay.de/itm/186679189985 incognito. Perhaps, eBay is once again using German eBay customers as guinea pigs for layout experiments. Comparable to laboratory rats. The eBay websites have become worse and worse in recent years. It used to be much, much better.
  20. This is the deactivated filter: ! https://github.com/uBlockOrigin/uAssets/issues/25247 ! ||www.ebay.$removeparam=_trksid But enabling this filter could lead to the reported problem: "Add to Watchlist" does not work .Anyway! This must be created under My rules in uBO to clean up the link completely: ||www.ebay.$removeparam=_trksid ||www.ebay.$removeparam=itmprp ||www.ebay.$removeparam=itmmeta
  21. Correct! I was not logged in at the time. The eBay link is in the format that you are offered as a simple guest. It actually only contains one real tracking component starting with _trksid, the other two are purely item related starting with itmprp (followed by a checksum) and itmmeta and are not normally filtered by tracking filters. The current URL tracking filter list inside uBO does not even clean _trksid, although it is included but not activated.
  22. Thanks for your suggestion! I'll try it out later on my Windows XP computer. Since Stylus no longer works in Mypal 68, and Stylish is no longer installed in New Moon 28, I will try to inject the code into the eBay pages via the userContent.css file. No success. This does not do anything. The issue doesn't seem to be related to animations and transitions. Only when blocking ebayimg.map.fastly.net in uBO, the CPU utilisation becomes normal again. But then the page looks unusable like that:
  23. Had to make a quick trip to the pharmacy. Just copied and pasted and bye-bye.
  24. Just for clarification. I know how to prevent URL tracking parameters. But the two profiles I am currently using are actually for testing and developing in New Moon 28 and Mypal 68. Apart from uBO, there is no other protection. And even this content blocker is only configured slightly, as it is not of interest. I test JavaScript and CSS files in these profiles. Mainly things I have created myself. I had searched for something on eBay there weeks ago, and now these pages no longer work as before. No more, no less. Nevertheless, thanks for replying!
  25. I just quoted the original link which worked much better some weeks ago. FYI, I always use uBlock Origin Legacy for filtering web content in New Moon 28. And in Mypal 68, uBlock Origin. And a few user scripts.
×
×
  • Create New...