Name not displayed on Winger button for restored windows

[supersaiyansubtlety]

• name is still there if I click on the Winger button
• name displays fine for windows created in current session
• name also displays fine after closing and re-opening an issue window with using History > Recently closed windows

Not sure if this is related to #20 because I'm using the builtin Firefox session restore, and it's the name on the Winger button not the actual window name.

Another extension could still be involved. I have Tabs Session Manager installed, but I'm restoring using the builtin History > Restore previous session (it used to restore the names on the Winger button, sorry I've had this issue a while so I'm not sure when it started).

Note that I'm actually using LibreWolf, but I doubt that matters.

[supersaiyansubtlety]

On Windows 10

[l10nelw]

Can you check if this is still an issue in the latest verson 2.4.0?

[supersaiyansubtlety]

It is still an issue

[supersaiyansubtlety]

A little more info:

• One window seems to always have its name displayed correctly (I think it's the first one to reopen but it's hard to say).
• Sometime the names do display correctly for all windows , I think when few windows are being restored (names worked just now when restoring 6 windows, they frequently don't work when restoring 10+ windows). nvm, basically the same 6 window session restored with names not displayed.

[l10nelw]

Thanks @supersaiyansubtlety. FYI I've switched to using my Windows 10 machine for the past few weeks, so far I haven't encountered the bug myself unfortunately.

[supersaiyansubtlety]

So it could just be coincidence, since the issue is inconsistent, but:
When winger auto-updated to 2.5.0, the names displayed properly on the launch when the update occurred, for three different instances.

[supersaiyansubtlety]

I think this is fixed in 2.8.0, perhaps because of the new label regex feature.

I haven't noticed it since setting label regex.

I also restarted a few times without regex to test and didn't see this issue.

[supersaiyansubtlety]

This happened again on a browser profile where I hadn't set any regex.

I added .* as regex and it immediately fixed itself, so there is at least a workaround.