First tab regularly does not retain address.

[wolfbeast]

The first tab on the tab bar regularly does not retain its address, and loads the home page instead when activated, even if the stored state has the proper title and favicon and everything.

I don't have exact steps to reproduce but it happens regularly enough to know it must be a flaw somewhere in this extension. This never happened with bartab.

[JustOff]

I've never seen this myself. Do you have any other tab/session add-ons installed?

As a guess, this could be somehow related to Pale-Moon#1640 (and should be fixed by it, if it's so).

[wolfbeast]

I don't have any other session add-ons installed. I do have "tab control" installed which adds a few handy options for my use but those should not interfere with the actual contents of suspended tabs. It think it may happen if I don't actually activate the tab in a session, so it never becomes active that session.

[wolfbeast]

It's quite possible that it is somehow related to that issue -- e.g. when lull the tabs initializes before the session is loaded? Might it pick up the (incorrect) home page URL in that case?

[JustOff]

I took a closer look to this, but unfortunately I still can't reproduce the problem or figure out how exactly Pale-Moon#1640 can affect LTT to cause such confusion. However, at the moment that issue remains the main suspect.

Meanwhile, could you please clarify your browser startup settings (General->Startup), where your home page points (local file, chrome url or remote site) and which LTT settings differ from defaults in your configuration?

[wolfbeast]

Session: restore windows and tabs from last time Home page: http://start.palemoon.org/

Changed prefs:

extensions.lull-the-tabs.autoUnload;true
extensions.lull-the-tabs.exceptionList;onlinepizza.se;docs.google.com;www.cloudflare.com;forum.palemoon.org;archive.org;192.168.0.10
extensions.lull-the-tabs.importBarTab;false
extensions.lull-the-tabs.leftIsNearest;true
extensions.lull-the-tabs.showButton;false

[JustOff]

Please report if this happens again on Pale Moon 27.9.0.

[wolfbeast]

I haven't seen this happening anymore in 27.9.0 so the sync loading of the session seems to have fixed this.

[JustOff]

Thanks for the confirmation. Let's hope it did it.