Extensions and custom buttons for UXP browsers - Corrections, modifications, adjustments, and special recommendations

[AstroSkipper]

1 hour ago, AstroSkipper said:

3 hours ago, UCyborg said:

I cannot get ReferenceError: nsIWebNavigation is not defined in Pale Moon when closing tab, only NM28.

Also can't break built-in session restore in either browser with all three extensions loaded, though I'm not sure what specifically to look for. The tabs I saved come back.

I can't really say whether the problem also occurs in Pale Moon (32-bit or 64-bit ), as I don't use this browser. It was also just a guess. In any case, the Speed Dial 0.9.6.18 and Tab Utilities 2.1.2 extensions in the latest New Moon 28 32-bit release definitely break the session restore function on my Windows XP system. The Session Manager extension only generates some errors in the Browser Console but is still working so far.

@UCyborg For reproducing this issue, it is simply enough to only use either Speed Dial or Tab Utilities. So, for example, disable Tab Utilities and Session Manager, start latest New Moon 28 (32-bit), close some tabs and restart the browser. Then you should actually notice that the already closed tabs are still there which means the internal session (re)store does not work anymore if Speed Dial is enabled. You should also see the error message "ReferenceError: nsIWebNavigation is not defined" in the Browser Console when closing tabs from the current browser session. The more tabs you close, the more error messages you will get. At least, that's what I observe in dirty or clean New Moon 28 (most recent version) profiles on my Windows XP 32-bit computer. And I'm pretty sure that I'm not the only one affected by this issue.  Maybe, other members may also confirm this issue. 

Edited October 4, 2024 by AstroSkipper
Update of content

[UCyborg]

Got it, depending on actions performed, you can get the session with wrong tabs, like you open 3 different tabs, close one of them, then session gets restored with all 3 instead of 2.

I think it can be solved by figuring out the cause of ReferenceError: nsIWebNavigation is not defined error, which as noted before, only happens on New Moon.

[AstroSkipper]

If anyone is wondering why I am bothering to post the issues with these extensions here, then the answer is very simple. I think the Speed Dial, Tab Utilities and also Session Manager extensions are important and worth keeping. I have been using them for years and would hate to see them go. This thread is dedicated to legacy extensions, and I hope that there is some way to make these particular extensions fully functional again. Be it that code changes are made to the UXP browsers or that the extensions are fixed. 

[AstroSkipper]

7 minutes ago, UCyborg said:

Got it, depending on actions performed, you can get the session with wrong tabs, like you open 3 different tabs, close one of them, then session gets restored with all 3 instead of 2.

Thanks for your confirmation!

8 minutes ago, UCyborg said:

I think it can be solved by figuring out the cause of ReferenceError: nsIWebNavigation is not defined error, which as noted before, only happens on New Moon.

If this issue only happens in New Moon 28 and not in Pale Moon, then there actually must have been a change to the UXP browser code which is causing it. Especially as in older releases of New Moon 28, I didn't notice this issue.

[roytam1]

3 hours ago, AstroSkipper said:

@UCyborg For reproducing this issue, it is simply enough to only use either Speed Dial or Tab Utilities. So, for example, disable Tab Utilities and Session Manager, start latest New Moon 28 (32-bit), close some tabs and restart the browser. Then you should actually notice that the already closed tabs are still there which means the internal session (re)store does not work anymore if Speed Dial is enabled. You should also see the error message "ReferenceError: nsIWebNavigation is not defined" in the Browser Console when closing tabs from the current browser session. The more tabs you close, the more error messages you will get. At least, that's what I observe in dirty or clean New Moon 28 (most recent version) profiles on my Windows XP 32-bit computer. And I'm pretty sure that I'm not the only one affected by this issue.  Maybe, other members may also confirm this issue. 

tried here but can't reproduce, it just restored correctly, and no error in js console:

[AstroSkipper]

21 minutes ago, roytam1 said:

tried here but can't reproduce, it just restored correctly, and no error in js console:

The issue happens in New Moon 28.10.7a1 (32-bit) with the build ID 20240922132822 (palemoon-28.10.7a1.win32-git-20240928-d849524bd-uxp-716b990183-xpmod.7z). Which browser version did you try?

Edited October 4, 2024 by AstroSkipper
Update of content

[roytam1]

12 minutes ago, AstroSkipper said:

The issue happens in New Moon 28.10.7a1 (32-bit) with the build ID 20240922132822 (palemoon-28.10.7a1.win32-git-20240928-d849524bd-uxp-716b990183-xpmod.7z). Which browser version did you try?

tried older build date july, and yet-to-be-released new build.

[AstroSkipper]

23 minutes ago, roytam1 said:

37 minutes ago, AstroSkipper said:

The issue happens in New Moon 28.10.7a1 (32-bit) with the build ID 20240922132822 (palemoon-28.10.7a1.win32-git-20240928-d849524bd-uxp-716b990183-xpmod.7z). Which browser version did you try?

tried older build date july, and yet-to-be-released new build.

That's exactly what I reported before. In older releases of New Moon 28, this issue didn't occur. I have just tested New Moon 28.10.7a1 (32-bit) with the build ID 20240718150512 (palemoon-28.10.7a1.win32-git-20240720-d849524bd-uxp-8fbf81bb8a-xpmod.7z), and the issue does not occur. That means there must have been a recent code change which makes this issue happen in New Moon 28.10.7a1 (32-bit) with the build ID 20240922132822 (palemoon-28.10.7a1.win32-git-20240928-d849524bd-uxp-716b990183-xpmod.7z).

[AstroSkipper]

@roytam1 Now we know that after this New Moon 28 release from the end of July 2024 the issue started to occur. So, it actually must have been a custom code change made by you as @UCyborg reported that the issue does not occur in Pale Moon. I am sure you will find the culprit and revert or fix it.  Thanks in advance!  

P.S.: I will later check from which release exactly this issue occurred for the first time.

Edited October 4, 2024 by AstroSkipper
Update of content

[AstroSkipper]

6 hours ago, AstroSkipper said:

@roytam1 Now we know that after this New Moon 28 release from the end of July 2024 the issue started to occur. So, it actually must have been a custom code change made by you as @UCyborg reported that the issue does not occur in Pale Moon. I am sure you will find the culprit and revert or fix it.  Thanks in advance!  

P.S.: I will later check from which release exactly this issue occurred for the first time.

@roytam1 I have just checked all releases starting after the end of July 2024. The Speed Dial issue "ReferenceError: nsIWebNavigation is not defined" definitely started with the release New Moon 28.10.7a1 (32-bit) with the build ID 20240922132822 (palemoon-28.10.7a1.win32-git-20240928-d849524bd-uxp-716b990183-xpmod.7z). And the Tab Utilities issue also started with this release. Both extensions seem to produce this ReferenceError issue due to the same code change made in the identified release and break the session (re)store. So, you have to check only the most recent (custom) changes. Hope this will help you.

Edited October 4, 2024 by AstroSkipper
Update of content

[AstroSkipper]

On 2/10/2024 at 7:29 PM, AstroSkipper said:

Restart & Purge - A custom button for restarting the browser and, if necessary, purging the startup cache, created by AstroSkipper

As I have already reported in @roytam1's browser thread, I have been investigating the restart behaviour of New Moon 28 and Serpent 52 (and also Mypal 68, but this is off-topic here) for some time with a focus on the startup cache. Unfortunately, I have not been able to find much useful information or documentation on this topic on the internet. Even my request in @roytam1's browser thread also went unanswered (addendum: in the meanwhile, @VistaLover has replied here. Thanks again for that! ). It seems that detailed information or knowledge about the startup cache and how the browser restart affects this cache is practically non-existent. The startup cache seems to be a replacement for the former Fastload. It resides in the profile directory to store continuous chunks of data in it. In my New Moon 28 installation, without using the custom folder chrome for scripts and CSS stylesheets, only one file resides there with the name startupCache.4.little. As both, the folder and file name, contain the string startupcache, one can conclude that data is stored inside this file to accelerate the startup of the browser. Which data exactly I really don't know.  I didn't find any meaningful documentation. I noticed that very often or in most cases the startup cache was cleared or reorganised automatically without any additional commands when restarting the browser. Sometimes, however, it remained unchanged after a restart. At least, I could find the code responsible for purging the startup cache.  Anyway! One thing is clear. If the data in the startup cache is corrupted, then starting problems can occur which only can be solved by deleting its content.
 
This can be done, for example, manually or by the commandline option -purgecaches. But there is no button or item to start this purge of the startup cache in a convenient way from within the UXP browsers. That's why I created a custom button for this purpose in JavaScript (rather a variant of JavaSript), the programming language used for creating new custom buttons by the extension Custom Buttons. I branded this custom button Restart & Purge. It performes a normal restart when left-clicked and additionally purges the startup cache when middle-clicked. After creation I have tested this custom button over a longer period of time, and it works for me as it should.
Here is a small screenshot of my custom button Restart & Purge and its tooltip taken from New Moon 28:



As the code of Restart & Purge 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:



The former download links unfortunately contained an XML backup file of the Restart & Purge custom button which either couldn't be installed without additional editing or some characters were not transferred correctly. The problem has to do with the conversion of custom buttons into XML format, where the tool I had used did not work correctly. This time I therefore provide a custom button link for direct install (when the extension Custom Buttons is already installed, of course ). Copy the quoted link below and open it in a new browser tab:

I can't insert the code of the link in this post! The MSFN forum editor is totally broken and hasn't been working properly for months especially when it comes to inserting of links. This has already reported multiple times! Well done, who is responsible for it!

Due to the shortcomings of the MSFN forum editor, I uploaded the custom button link of Restart & Purge as an HTML file. Here is the download link: https://www.mediafire.com/file/nrqim7ek9s6gp07/CB_button_Restart_%26_Purge.html/file
Simply open this HTML file in a browser tab and click the embedded custom button link for Restart & Purge! 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
And since the legacy Custom Buttons extension runs in the UXP browsers, my custom button Restart & Purge can be used in New Moon 28, Serpent 52, Pale Moon and some other browsers.

Greetings, AstroSkipper

I have updated the code of my custom button Restart & Purge to let it run the fully native restart code inside the UXP browsers to avoid any abnormalities. Restart & Purge v2.0 will be released soon after some additional tests. In any case, it should work then with New Moon 28, Serpent, Firefox 52esr and even the non-UXP browser Mypal 68. 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.

Cheers, AstroSkipper

Edited October 5, 2024 by AstroSkipper
Update of content

[Mathwiz]

On 10/4/2024 at 4:02 AM, UCyborg said:

This is with following When New Moon starts setting, though it doesn't seem likely that it matters:

I'm not sure if that setting matters, but NHTPG doesn't use it. (We discussed it on @roytam1's thread.) His bug only occurs under certain conditions:

• Using a Serpent 52 version newer than July 2023
• Using the Photonic theme
• Not using multiprocess mode
• Killing the Serpent process with task manager to force the restore session dialog (this is only done when the browser gets too slow due to the gradual build-up of memory-hogging Javacrap. NHTPG normally prefers to start his browser sessions "clean.")

So it seems to be some sort of incompatibility between some change made in Serpent in August 2023 and the Photonic theme, but darned if I know what it could be.

[UCyborg]

I spotted this funny issue on New Moon last time when disabling Session Manager, unsure if it was related to forgotten "Ci" in the code.

[AstroSkipper]

My German language pack for New Moon 28 - Fixed - Part 5

My last German language pack 28.10.0rc6 from this post had to be fixed again. Due to some new entities, the tab Advanced in the Preferences window is broken in the most recent release of New Moon 28. Here is a screenshot to demonstrate this issue:



I have fixed this issue and assigned the number 28.10.0rc7 to the new, corrected version. Here is a screenshot taken from the fixed version:



And here is the download link of the updated German language package 28.10.0rc7 for the more recent versions of New Moon 28: https://www.mediafire.com/file/xw8470f969vozwg/de-28.10.0_RC7.xpi/file

Greetings from Germany, AstroSkipper

Edited October 6, 2024 by AstroSkipper

[NotHereToPlayGames]

1 hour ago, UCyborg said:

unsure if it was related to forgotten "Ci" in the code.

The file structures inside omni.ja are of course different for New Moon 28 and Serpent 52.  I could not find any missing browser.webNavigation.stop(Ci.nsIWebNavigation.STOP_ALL); in Serpent 52.