Bewertungen für Select After Closing Current
Select After Closing Current von jingyu9575
Bewertungen von Firefox-Benutzer 14349265
Bewertet mit 3 von 5 Sternen
von Firefox-Benutzer 14349265, vor 7 JahrenI have issue with this addon working together with Simple Tab Groups (by Drive4k).
Occasionaly, when switching between tab groups, last selected tab (I mean current active tab) "moves" to switched group and "stays" there as last tab.
I was unable to reproduce this reliably to find exact cirquimstances.
Disabling either of these two addons of course removes the issue.
=======
Update: I have figured this issue out.
When I switch from group A to group B and then right away close active tab in this B group - I am switched back to A group. That works like it should be: last active tab becomes that one in A group.
But if I switch back to group B again - then any active tab from A "moves" to group B.
Disabling your addon resolves this issue.
Occasionaly, when switching between tab groups, last selected tab (I mean current active tab) "moves" to switched group and "stays" there as last tab.
I was unable to reproduce this reliably to find exact cirquimstances.
Disabling either of these two addons of course removes the issue.
=======
Update: I have figured this issue out.
When I switch from group A to group B and then right away close active tab in this B group - I am switched back to A group. That works like it should be: last active tab becomes that one in A group.
But if I switch back to group B again - then any active tab from A "moves" to group B.
Disabling your addon resolves this issue.
Antwort des Entwicklers
geschrieben am vor 7 JahrenI reported this issue to Simple Tab Groups, and the developer has fixed it in v3.3.2.
https://github.com/Drive4ik/simple-tab-groups/issues/271
Edit: v3.3.3 seems to have this problem again. I have reported the regression.
Edit: v3.3.4 fixed it.
https://github.com/Drive4ik/simple-tab-groups/issues/271
Edit: v3.3.3 seems to have this problem again. I have reported the regression.
Edit: v3.3.4 fixed it.