Leaderboard

If by 'standalone' you mean a portable version, yes there is. If you are going to continue using Supermium, please continue this in the Supermium thread.

The 'dog account' (Jaguarek62) posted on October 29th in another thread on a completely different subject, so it is still active. No forum rules have been explicitly broken here yet, and I trust people will be aware and careful about this.

I sincerely hope that constantly posting offtopic isn't a form of senility. In the last few pages, one doesn't get anything about the actual topic here. @roytam1 must have a very thick skin.

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.