Plus, it still doesn't fix all reported annoyances with the new tab dragging behavior triggering Minimize Active Tab on drag: [VB-77817] Tab dragging with "Minimize Active Tab" is terrible Yes, it's still terrible with tabs in the second bar. The tab does get dragged, but the whole UI switches to the last used tab. Which means: If the last active tab was a single tab, an unlocked second bar disappears completely, which prompts the tab in the second bar to no longer be dragged. This means the tab will appear un-draggable to the user. If the last active tab was a stack, the second bar switches to a completely different set of tabs. This means the user will accidentally move their active tab into a completely different stack. If I were to rephrase those older issues now, I would say it (sadly) still is as follows: Issue aa (old) 0. Use two tab bars and have the second bar unlocked. Use Tab A (unstacked). Switch to Tab B in Stack 1. Drag Tab B. By dragging, you clicked on the Active Tab. Minimize Active Tab is triggered, switching you back to Tab A and making the second tab bar disappear. But what happens to Tab B? Well, since you were dragging Tab B, an element which has since ceased to exist (because the second tab bar disappeared), your dragged tab ceases to exist, which makes Tab B appear undraggable. Issue bb (old) 0. Use two tab bars. Use Tab A in Stack 1. Switch to Tab B in Stack 2. 2.5 Our goal here is to drag Tab B to another position in Stack 2. Drag Tab B. By dragging, you clicked on the Active Tab. Minimize Active Tab is triggered, switching you back to Tab A and switching the set of tabs on the second tab bar to tabs in Stack 1. You, the user, are now dragging tab B through positions inside Stack 1 instead of dragging tab B through positions inside Stack 2, as the user intended. If anyone is up for reproducing and acknowledging those older issues (introduced with the new tab dragging behavior) in hopes of a fix or want to let me know that they are not issues but intended behavior, contact me here. Otherwise, consider this the last time I report those issues from scratch again. I may link to this post in the future, I will continue loving, using and supporting the browser, but I won't spend any extra hour describing issues that will never be acknowledged nor fixed nor marked as false positives on my radar, because all the effort invested proves to be utterly wasted. That being said, this is the exception and not the rule. I can only be glad most issues I personally reported got fixed sooner or later. Last I could do is make a feature request, but fixing those issues (by reverting to the old system where a drag isn't a click which would mean that Minimize Active Tab would not trigger on drag; if that is even possible) hardly counts as a feature.