VimFx is disabled when moving multiple tabs to another window

[neeshy]

Steps to reproduce: Shift-click tabs from one window and drag them to another window.

Now VimFx will only function in the first tab moved over. Shift-escape doesn't seem to fix it. The issue seems to go away once the tab is unloaded (about:unloads) and reloaded.

I've also triggered the same issue when going back and forth in history, but it's harder to reproduce that way.

I'm on Linux w/ Firefox 111.0.1, VimFx 0.25.0 and LegacyFox 3.0 (w/ the BootstrapLoader sandbox fix).

[girst]

I'm assuming with "disabled" you mean broken, right? VimFx's icon is not red or silver, but green/colored? Unfortunately, there are some bugs with VimFx not being loaded into browser windows correctly sometimes. Another instance I discovered is when undocking a tab into a seperate window, and then re-docking it into the original window.

I've been getting bit by the history back bug lately, too, and even more unfortunately I don't have an idea what causes this class of bug.

[girst]

I did some sifting through the firefox sources and I think all those bugs are related to Fission, somehow. Unfortunately, I can't get it reproduced in mozregression/nightly, and the error comes from the c++ innards of firefox (which is a pain to debug, so i didn't). can you disable fission[1] (about:config -> fission.autostart -> false, then restart the browser) and see if you can reproduce the bug(s)? i feel compelled to warn you that fission is a safety measure against browser bugs, so keep it disabled at your own responsibility. [1]: https://wiki.mozilla.org/Project_Fission

[girst]

i can reliably break and unbreak firefox with fission.autostart;true by just toggling fission.bfcacheInParent (false=>good, true(default)=>bad). @neeshy, please disregard the previous instructions and set fission.bfcacheInParent to false instead!

[neeshy]

Thank you for investigating, and sorry for the late reply. On my end, the moving multiple tabs bug still occurs even after setting fission.bfcacheInParent to false. Likewise with fission.autostart. I'm not sure about the history back bug since I can't consistently reproduce it regardless of those fission settings.

[Kallinteris-Andreas]

Same here, changing fission.bfcacheInParent and fission.autostart

and as far as I can tell, it is not possible to disable the "dragging tabs causes them to detach in a new window" behavior