[v5] Unable to reopen the URLs already included in a container in another container

[wordpure]

If a URL is already included in a container, it will still end up being opened in the including container, even if you choose to reopen in another container in the context menu.

This is not convenient for temporarily switching containers, is there an option to change its behavior?

[dexeonify]

With the latest beta release, reopening a tab included in a container in another container through the context menu is fixed. But if you try to do the same with the new tab buttons/shortcuts, it won't work. In other words, middle clicking on the new tab button should reopen the current tab in default container, regardless of the container settings, for the current session.

[wordpure]

With the latest beta release, reopening a tab included in a container in another container through the context menu is fixed.

Thanks for the great work, in 5.0.0.rc5, reopening in other containers works fine. However, I found that when reopening, the tab bar will flicker briefly due to new and close tabs. Is it possible to avoid this by hiding tabs?

But if you try to do the same with the new tab buttons/shortcuts, it won't work.

It is indeed a pity that the container state of the current tab cannot be inherited. Currently I use multifoxContainer, a UserChrome Scripts, to achieve this function.

[mbnuqw]

However, I found that when reopening, the tab bar will flicker briefly due to new and close tabs. Is it possible to avoid this by hiding tabs?

Not possible.

[mbnuqw]

Resolved in v5.0.0