AstroSkipper

That would be great. The less bugs, the better. Isn't it? Now, I have observed another problem in Mypal 68.14.4b, a real bug, so to speak. Sorry for that in advance! Copying a selected text from a website to the clipboard and then reading it from the clipboard does not work properly when doing it via JavaScript. Although copy and paste natively works, it doesn't work correctly via a script or a code input from the Browser Console. Here is my test code I created to demonstrate the problem. Open a website with a text area, select some text or words, then open the Scratchpad (Enviroment -> Browser) and of course the Browser Console. Now, execute my code snippet: // Test code window.focus(); goDoCommand("cmd_copy"); var clip = gClipboard.read(); console.log(clip); You should then notice in the Browser Console that after the first execution, the logged value of the variable clip is not equal to the currently selected text but equal to the previous content of the clipboard. You get the correct and desired value of the variable clip only after a directly following, second execution of the code. So, only executing the code twice leads to the correct result instead of once. Any ideas? P.S: I should still mention that contrary to Mypal 68, this test code correctly works in @roytam1's New Moon 28.

No, that doesn't mean I've done anything wrong at all . In case of calling up the about:preferences#privacy page, then opening the native "Manage Cookies and Site Data" popup and deleting a cookie, seriously, what can you do wrong? Absolutely nothing! Anyway! I can't confirm your statement. When deleting a cookie in Mypal 68.14.4b, even in a fresh, untouched profile, I always get the same error message: Services.lsm is undefined ClearDataService.jsm:488 deleteByHost resource://gre/modules/ClearDataService.jsm:488 It was just a kindness on my part to point this error out to you. And so that you can get a better impression of the error, I have this for you: So, what can you do wrong when deleting a cookie?

Perhaps, someone is now wondering what is so special about the "Manage Cookies and Site Data" custom button. The answer is quite simple. There is no functioning extension or toolbar button for the Quantum browser Mypal 68 that can simply call up the native, internal cookie manager only. In contrast to the UXP browsers, the direct call of the corresponding XUL file is unfortunately no longer sufficient because it doesn't work correctly. Call it a bug, an issue or whatever, in any case, it is faulty. This custom button seems to be therefore unique. Contrary to the native popup, to which you first have to click through, It calls up the internal cookie manager by only one click in an own, resizable window. BTW, creating custom buttons for UXP browsers is much easier and much more fun. In the Quantum browser Mypal 68, most things no longer work as easily or at all. Everything is very restrictive and obstructed.

Ok. I was able to improve a bit my custom button for calling up the "Manage Cookies and Site Data" window. Both, the about:preferences#privacy and three seconds later the desired dialogue are now loaded in the same chrome window which avoids an additional loading of a tab. Nevertheless, I hope that there is a better solution yet. As custom buttons are actually the topic of this thread, I have decided to post about this stuff here again. My project of creating a custom button to directly call up the "Manage Cookies and Site Data" dialogue in Mypal 68 seems to have come to a temporary end. It works perfectly. I have solved the issues encountered in my own way and I am currently in testing mode. Here is a short preview:

@feodor2 While developing my custom button for calling up the "Manage Cookies and Site Data" window, I found a further bug in Mypal 68. When calling up the about:preferences#privacy page, then opening the "Manage Cookies and Site Data" popup and deleting a cookie, you always get the following error message: Services.lsm is undefined ClearDataService.jsm:488 deleteByHost resource://gre/modules/ClearDataService.jsm:488 I can't find the "Services.lsm" anywhere in the omni.ja files. LSM = localStorage Manager? Anyway! I'm not surprised that this piece of nowhere is not defined.

Ok. I was able to improve a bit my custom button for calling up the "Manage Cookies and Site Data" window. Both, the about:preferences#privacy and three seconds later the desired dialogue are now loaded in the same chrome window which avoids an additional loading of a tab. Nevertheless, I hope that there is a better solution yet.

@feodor2 Calling up chrome://browser/content/preferences/siteDataSettings.xul directly does not show the most recent cookie database. When calling up the about:preferences page beforehand, the most recent cookie database is shown, and the XUL file call works again correctly. Do you know how to do in JavaScript the same what calling up the about:preferences page does in terms of the cookies? I need the part of the code that is executed by the call to the about:preferences page regarding cookies before I call up the chrome://browser/content/preferences/siteDataSettings.xul file. As I mentioned, I am in the process of creating a Cookie Button which opens the dialogue "Manage Cookies and Site Data". My current version automatically opens the about:preferences#privacy page and three seconds later the wanted dialogue in an own chrome window. This indeed works properly but actually I would like to avoid opening an about:preferences#privacy tab by doing the necessary commands internally via JavaScript. I already tried a lot but without any success. So, any ideas?

Ok. I understand that very well. Completing the new version is a much higher priority. But one thing is clear. A bug is a bug. Or call it an issue, an unwanted behaviour or whatever. Regardless of whether you don't consider it important or don't want to fix it. Calling the cookie GUI via its XUL file directly is faulty. I have investigated and documented it in detail. The script is the same, it is heavy obfuscated and refuses to work too if to block the connection to its site, very suspicious so not suitable. No need to block its connection. The script is simply great. Sometimes, one has to trust. Without trust you can't do anything when using software, scripts and similar made by others. Would be great to have document.loadOverlay() back in Mypal 68.

@feodor2 The non-standard JavaScript function document.loadOverlay() is deprecated since Gecko 60 (Firefox 60). Did you completely remove it in Mypal 68? Some of my (important) scripts call up this function which leads to the error message "TypeError: document.loadOverlay is not a function" in the Browser Console. If it has been removed, can it be re-implemented? I ask this as in more recent Firefox versions, these problematic scripts seem to be working again which means the document.loadOverlay() method is there again and works.

Hope you can fix this bug. If it was fixed, my self-created custom button would work as I planned without any special workaround to be implemented. I use the VORAPIS V3 script version. Works great here in Mypal 68.

@feodor2 Thanks for the links! The history feature of GitHub is great. Thanks to @UCyborg's hint to use this time machine, I started downloading repositories from the Firefox 68 era. With the linked version of xiaxiaofloods's userChromeJS, you can indeed install bootstrapped, legacy extensions in Mypal 68, but unfortunately, none of xiaxiaofloods's extensions I've tested from the linked repository do actually work.

Personally, I would tend to agree to this: Mypal 68 ≈ Firefox (≥ 68). In many ways, Mypal 68 behaves like a normal Firefox browser, but not in all. The JavaScript engine, for example, is comparable to that of higher versions. Mypal 68 is a Quantum browser, which has made it quite difficult to enable the use of UC.JS scripts, for example. The download package MYPAL_68_CB_requirements.7z from my first post is not available anywhere. It is very specific, and stops working in Firefox 72+ due to some code changes. I put together the configuration files myself to make it really work. In higher Firefox versions, the script functionality seems to be much easier to activate. BTW, one file of my package spits out an error in the Browser Console, which I fixed in the meanwhile.

I never did that before. How do you go back to an earlier point in a project?

FYI, I have tested this, and it doesn't work for me in Mypal 68. Neither the implementation for loading of scripts nor the one for loading of specially adapted bootstrapped extensions from xiaoxiaoflood's project userChromeJS works in Mypal 68.14.4b. The whole project seems to be related to more recent versions of Firefox. Here is a quotation from the GitHub page: The specially adapted bootstrapped extension Download Manager (S3), for example, targets Firefox 125.0a1 and higher.

@feodor2 I noticed this issue when creating a custom button for calling up the cookie manager. For reproducing this issue, call up chrome://browser/content/preferences/siteDataSettings.xul, delete a site cookie of your choice, close it, open the site whose cookie you deleted and call up chrome://browser/content/preferences/siteDataSettings.xul again. You will then notice its cookie is not listed although it is there. And when now restarting the browser, the call up of this internal chrome site leads to an empty, broken and non-functional interface. Here is a screenshot of this issue including the TypeError message Uncaught TypeError: this._getQuotaUsagePromise is null SiteDataManager.jsm:255:5 getSites resource:///modules/SiteDataManager.jsm:255 init chrome://browser/content/preferences/siteDataSettings.js:127 onload chrome://browser/content/preferences/siteDataSettings.xul:1 in the Browser Console: Only by calling up the about:preferences page will it work again. BTW, when doing so in an UXP browser as, for example, New Moon 28 or Serpent 52 by calling up chrome://browser/content/preferences/cookies.xul, there is no such problem.

@feodor2 When calling up the internal site chrome://browser/content/preferences/siteDataSettings.xul in Mypal 68.14.4b directly, the list of all cookies is not up to date in most cases. Only when you call up the about:preferences page beforehand, you get a current list of all cookies. Actually that can't be the intention. Right? So, is this a bug or really by design? When calling up the internal site chrome://browser/content/preferences/siteDataSettings.xul directly after browser restart, it is empty, broken and non-functional.

This is not quite so easy. One thing in advance. The chrome folder and the UC.JS scripts have absolutely nothing to do with the legacy custom buttons. You have to install a legacy Custom Buttons extension in the Quantum browser Mypal 68 which supports natively webextensions only. To do this, the signature check of extensions must be switched off by a special hack, as most of all legacy Custom Buttons extensions are unsigned. The hack then has to be patched again , and a few prefs have to be set. Finally, you have to check whether your legacy Custom Buttons version can be installed at all and properly works under these conditions. All in all, not so easy as it may seem. Right? Furthermore, the code of custom buttons must of course be designed for Mypal 68 in such a way that it takes the newer JavaScript engine into account. Many (legacy) custom buttons that run in the UXP browsers therefore do not work in Mypal 68. And as you already know, even a custom button working in New Moon 28 does not necessarily run, for example, in Serpent 52. However, if all is done correctly, it should look like this way: This is a screenshot taken from the Add-ons Manager in Mypal 68.14.4b. All of these custom buttons are working fine in Mypal 68, and there are more, of course. It's just a test profile. BTW, three of these six custom buttons have been created by me and are also working in all my UXP browsers.

A RAM consumption of round about 700 MB for only one YouTube video?

How do you expect us to help you if you cannot even tell us the EXACT version we are to compare with ??? The answer is very simple. You don't have to help those types. It's more of a waste of time. And I also don't believe that old browser versions from 2022 work better with YouTube today than the current ones. YouTube has permanently changed for the worse. Even an old cucumber doesn't really help.

The old Custom Buttons forum had gone long time ago. Personally, I have the most important things in my archive, which I have been maintaining for decades. So, I need practically nothing from the old forum although it is a great pity that it no longer exists. And you should also be aware that many old custom buttons are no longer compatible with newer Firefox or Firefox-based browser versions. And by that I also mean Firefox 52, which is the origin of many forks.

<sarcasm font>Is this your swan song?</sarcasm font> I love the creativity of some people here. BTW, your investigations of the VORAPIS V3 interface are strange. On my old and very weak Windows XP computer, the original YouTube interface is a real disaster. It takes ages to load and only with tons of scripts, filters and extensions, it can be accessed but when scrolling the page a bit, the loading of unwanted crap starts again with a 100% CPU usage. In contrast, the VORAPIS V3 interface is loaded in less than a minute, and the usage of CPU and RAM is much, much less as it is with the original interface, even when scrolling the page a bit. So, no swan song but stating facts.

Restart & Purge v2.0 - A custom button for restarting the browser and, if necessary, purging the startup cache, created by AstroSkipper Due to some abnormalities I observed when using my Restart & Purge custom button, I have now updated it to the version 2.0. I have changed and reworked the code considerably, and after a lot of testing, this updated custom button now works perfectly. One of the changes is that this new version of Restart & Purge now calls up the native restart code from the browser inside. The old version wasn't bad though, but the new one is definitely better and more compatible. I think there should no longer be any problems that could have occurred in very rare cases. Restart buttons are available in abundance and are nothing special. However, the most interesting feature of this custom button is the ability to purge the startup cache and restart the browser with one click. There are no corresponding extensions or functions with which the startup cache can be quickly deleted in the UXP browsers. In New Moon 28 not even the command line option -purgecaches works. So, an alternative way to delete the startup cache would therefore only be manually via the Windows Explorer or a file manager. My Restart & Purge v2.0 custom button performes a normal restart when left-clicked and additionally purges the startup cache when middle-clicked. Here is a small screenshot of my custom button Restart & Purge v2.0 and its tooltip taken from New Moon 28: As the code of Restart & Purge v2.0 has to be initialised, you won't find it in the tab "Code" but in the tab "Initialization code" of this custom button. Here is a screenshot of its code: And here is the download link: https://www.mediafire.com/file/1myts3tqkr6lgrv/Restart_%26_Purge_v2.0_10-12-24.xml/file The download link contains an XML backup file of the Restart & Purge v2.0 custom button as the problem with the conversion of custom buttons into XML format has been finally solved by me. Simply open the XML file in the browser and click onto the install button! For the installation of this button, the extension Custom Buttons is required which you can get 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 My custom button Restart & Purge v2.0 can be used with New Moon, Serpent, Firefox,even with the non-UXP browser Mypal 68 and some other browsers. And most probably also with Pale Moon and Basilisk (the call up of the native restart code should be the same as in the other browsers) which I can't test, though. Greetings from Germany, AstroSkipper

I avoid the original YouTube interface as it has become useless for me the last years. I use instead the VORAPIS V3 script which is really great. I therefore no longer notice whether the original interface has become even worse.

BTW, it wasn't meant offensive. It was just an observation I made when reading your comments. I'm someone who likes to say what I think, sometimes very directly. And as for Rammstein, I'm sorry to say that I've never been a fan.

There's a well-known American moron whose saying I'll use here in a modified form anyway: Make old code great again!