Tabs not loading and more

[webscot]

I attempt to restore in same window or new and none of the tabs load the icons anymore. Yesterday, I had to extract all of the links from the lazy load links that were pre-loaded in each tab. None would load the saved URL. Today, it's even worse. Most of the tabs did not load from the saved session. New Tab tabs were added that are blank despite the tab links being there. Also, when I click the Session Sync browser icon for the drop-down, it now always says window 1. I must select the saved session to re-save (overwrite) or to see the saved links.

[ReDEnergy]

Unfortunately seems that I did not test enough the history auto-save support with the default Firefox lazy loading :(. I have removed the old custom implementation of lazy loading and switched to Firefox built-in but it seems that they are incompatible and nothing it will be saved in history if a tab is unloaded (lazy loaded). It's a critical bug and I will try to find a solution asap for it.

Sorry for the issue.

[webscot]

I have further noticed that the last overwrite did not save the URLs or titles. Instead, it merely saved the URL as the title without any actual URL.

[webscot]

Wow. That was quick. Thank you.

[ReDEnergy]

Yes, sadly that's the incompatibility I was talking about. It seems the unloaded tabs are not containing the information similar with a normal tab and the addon fails to properly display it or show it.

[ReDEnergy]

I know it's not nice but to prevent more issue you should disable lazy loading :(

[webscot]

Just so you know...What is strange is that I clicked all of the tabs after seeing no favicon to load them all before my last overwrite. The result was just the URL name with no title, favicon, or link.

[webscot]

So, is the lazy loading a lost function for now until there is a change in FF?

[ReDEnergy]

Unfortunately the update I made was a bad decision and at this point I don't know for sure if I should try to revert to the old implementation or not. At the same time I have little time to update the implementation right now, at least for the next 2 weeks I definitely can't have it updated. Will try to think/find a solution and get back to you. Firefox definitely won't change the way it was designed so either I try to fix things myself or leave things as they are which is definitely not ok.

[webscot]

Thank you for responding. Just thinking out load...since AI is all the rage right now, have you tried anything like Claude Code to ask it to massage the code to overcome the issue? Maybe a time-saving idea.

[ReDEnergy]

I use AI at work and for some personal projects, even for the latest update for this addon I used it extensively to port the addon to a newly framework that should make the addon more easily to update in the future.
The thing with AI is that even though it might help and sometimes it can give you a lot of things I personally don't let it run freely or trust what it does without making sure I can still control the output and understand all the changes it does. If you blindly trust AI and let it change stuff, thing might look that they work but in reality it may not work perfectly. So I still have to take the time to validate, test, pack, launch the update. Maybe I can do all this in a day but right now I really don't have time for this to invest.

I really care about the addon, and will definitely update it if it will stop working but I also have other stuff more important to fix/work/promises to do and sadly this is last on the list 🙁.

At some point in life you have time for A or B. Currently a lot of other things are more valuable for me or need to be addressed fast than updating the addon. The code is public and others can at any moment clone the project and use AI to fix or implement things for themselves. The reality is that almost nobody does that because in this case the project is just good for a very small niche of users, so there's little interest to do so. I no longer want to make any promises that I can't keep but I know for sure in this case I need to fix something because I introduced a bug that killed a feature that many may have used. I will try to fix it but it will be the earliest I can find the time to invest into it.