AstroSkipper

@feodor2 I am not sure if you aware of this. The logger of uBlock Origin 1.60 does not work in Mypal 68.14.4b when running single-process mode. Neither in the officially last compatible version 1.46 of uBlock Origin. In multiprocess mode, the logger is running fine.

Your assumption is unfortunately wrong. If you had read my article carefully, you would have noticed that the All about: custom button is not a fork of an extension but of an old custom button. When I create or fork custom buttons, then a well-functioning toolbar button is the main target. So, using the All about: custom button means using the toolbar button. That's why it is called custom button and not extension. I could implement such functionality you requested but I am not interested in. Personally, I am a fan of toolbar buttons with multiple and meaningful functions.

All about: - A custom button for accessing the about:config page and other important about:pages in a more convenient way. Forked, translated and reworked by AstroSkipper All about: is a custom button to open the about:config page solely, or alternatively, with a currently selected or a previously copied string as a filter. Furthermore, other important about:pages can be easily opened from a button menu each with one click. I created two versions, one is targeting Serpent, Basilisk and other Firefox 52/53 based browsers, and the other is targeting the New Moon and Pale Moon browsers. I forked the All about: custom button from an old but still working one, translated and completely reworked it. I changed the content of the tooltip, added a help menu, inserted icons to the about:pages button menu by adding code, adapted the about:pages entries to the respective browser versions which lead to two different versions. All has been done solely in JavaScript without the help of CSS. Finally, I rearranged some code. The All about: custom button is very handy and helpful for those who are working a lot with prefs in the about:config page. The most interesting features are to open the about:config page with the currently selected string without copying it and a button menu with only important about:pages. Here are small screenshots of the All about: custom button taken from New Moon 28: And here are the download links: All about: for Serpent, Basilisk and other Firefox 52/53 based browsers: https://www.mediafire.com/file/16sfrr2gxwdxdc7/All_about-fx-sp-ba.xml/file All about: for New Moon and Pale Moon browsers: https://www.mediafire.com/file/gyktk1qu92k003g/All_about-nm-pm.xml/file The download links contain XML backup files of the All about: 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 The custom button All about: can be used with New Moon, Serpent, Firefox. Most probably also with Pale Moon and Basilisk which I haven't tested, though, as I don't use these browsers. Unfortunately, these versions of the All about: custom button don't work with the non-UXP browser Mypal 68 and other modern Firefox versions as the used code is not compatible with them. But for Mypal 68, I already created a new All about: custom button from scratch with same functionality since I also use the legacy Custom Buttons extension in this browser. Its creation was much more complicated as I thought due to some issues I had to fix and due to a complete recreation of the button menu. The custom button looks absolutely identical to the UXP variant but its code inside is of course different. Greetings from Germany, AstroSkipper

Personally, I don't expect to be able to surf every website properly with UXP browsers. The bloated, modern and totally over-greedy websites simply have to be accessed with other browsers or devices. Since there's a lot of Googlised junk on them, such sites are thrown at my Android (Google) tablet. That works great. Spoken for me only, I don't like the modern web layout. In my opinion, the entire development of websites is going in the completely wrong direction. I would rather focus on fast page loading and compatibility than overloading pages with all kinds of bells and whistles.

After more in-depth investigations, tests and analyses , I have come to the conclusion that the issue, described in my previous posts, is primarily a timing problem in multiprocess mode and can be easily fixed by inserting a delay in the right position.

@feodor2 To be even more precise, the actual culprit is the command goDoCommand("cmd_copy") if used in multiprocess mode only for fetching selected content on a page without actively copying it via Ctrl+C or using an associated copy feature in the form of a menu item or button. Normal copying content with this command works correctly. BTW, I am only talking here about the native command goDoCommand("cmd_copy") without the help of specialised extensions or scripts. For the purpose of copying selected content automatically to the clipboard, there are a lot of extensions or user scripts. Needless to say, I don't know if it is possible to fix it natively in Mypal 68. However, I personally found different solutions to circumvent this issue or bug in my coding project without the help of specialised extensions or user scripts. Whether the ideas of my solutions can be used for a native fix in Mypal 68 or not, I can't assess. Nevertheless, if you are interested in, please let me know!

@feodor2 Again, same problem as quoted above but a bit more detailed. If you select a word on a page In New Moon or Serpent, the command goDoCommand("cmd_copy") in combination with the gClipboard.read() method fetches this selected word first and only then the last copied content from the clipboard during a second, following execution. In Mypal 68 (running in multiprocess mode), it is unfortunately the other way round. For me, it looks like an issue of execution priorities. So, my request. Can you restore the original execution order when this combination of commands is used in your browser such as it is in New Moon or Serpent? And just as a further information, the combination of the commands goDoCommand("cmd_copy") and goDoCommand("cmd_paste") works correctly in Mypal 68, though. Same applies to the gClipboard.read() method which solely executed also works correctly. @feodor2 After some tests, I can confirm that the issue I reported in my previous posts only happens in multiprocess mode. When running Mypal 68 in single-process mode, the command goDoCommand("cmd_copy") in combination with the gClipboard.read() method works correctly such as it is in New Moon or in Serpent. So, it is definitely a multiprocess mode issue. BTW, I really love to talk to myself.

@feodor2 Again, same problem as quoted above but a bit more detailed. If you select a word on a page In New Moon or Serpent, the command goDoCommand("cmd_copy") in combination with the gClipboard.read() method fetches this selected word first and only then the last copied content from the clipboard during a second, following execution. In Mypal 68 when running in multiprocess mode, it is unfortunately the other way round. For me, it looks like an issue of execution priorities. So, my request. Can you restore the original execution order in Mypal 68's multiprocess mode when this combination of commands is used in your browser such as it is in Mypal 68's single-process mode, in New Moon or in Serpent? And just as a further information, the combination of the commands goDoCommand("cmd_copy") and goDoCommand("cmd_paste") works correctly in Mypal 68, though. Same applies to the gClipboard.read() method which solely executed also works correctly.

That's correct, and I was aware of this. But as most of @roytam1's browser editions are based on Firefox 52, I deliberately excluded Serpent 55. No, I didn't miss it. But I couldn't see any reference to the legacy UXP browsers. And this thread is not about Chrome or Chromium browser. Hence my comment.

Just as I assumed! And that's why I prefer Windows 10 Firewall Control Plus XP when it comes to firewalls under Windows XP. Never had such problems. Most of computer problems are rather home-made.

I agree with that. You can still surf well with New Moon 28 (and Serpent too). And I can confidently do without the overloaded, newfangled and resource-hungry pages in the UXP browsers.

Works fine here. AdGuard lists have been updated successfully just now by uBlock Origin Legacy 1.16.4.35 in New Moon 28. So, I can't confirm your observation.

I just stated facts. I do not make it look anything. But you didn't mention in your previous posts which version of AdNauseam you was using, what advantages this extension might have over uBO that prompted you to install it and which UXP browser you was actually talking about. And any Chrome/Chromium experiences and CRX extensions are indeed offtopic here and misleading. No more, no less.

CRX files are extensions for Chrome/Chromium browsers. Are you aware that this thread here is dedicated to @roytam1's browser releases? They are all based on Firefox up to version 52. So, what are you talking here about?

AdNauseam v3.7.802 is the last version for legacy Firefox browsers. It is from 28.09.2018 and based on uBlock Origin 1.15.24 which is of course older than the last, official (legacy) version uBlock Origin 1.16.4.30 or 1.16.4.31b2. So, what are the advantages supposed to be?

There is no problem with IceApe. I can easily connect to all websites. Here is a screenshot regarding the https://o.rthost.win/ site: Either your browser is misconfigured or something is blocking some of your connections. Check your network settings, internet connection settings, security settings, and update your root certificates! In any case, the problem is on your side. And don't forget that the problem can also be sitting in front of the computer! (Old computer wisdom.)

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.