-
Notifications
You must be signed in to change notification settings - Fork 27
Pulling tabs into new group results in wrong tab being closed #9
Comments
This bug really prevents me from using Tab Sugar at all, much less being able to do further testing. I'm running into other odd issues, but this is pretty much step one of actually using the extension and makes further testing/bug reporting mostly useless. |
After a deep analysis, I'll have to cover both BI04 (Attach a tab to a window) & BI06 (Detach a tab from a window) interactions before being able to reuse 'em for the DI06 (Move a tab to the dashboard) & DI08 (Move a tab to an existing group). |
I can see how these would be related. It is a lot of work, but look on the bright side. Once you get BI04 and BI06 working, you'll have most of the functionality done! |
I implemented both BI04 (Attach a tab to a window) & BI06 (Detach a tab from a window) interactions with the 0.9.25 release. |
Version: 0.9.23
Steps: 1. Open Tab Sugar with the current set of tabs (at least 2) being all in the default group.
2. Pull any tab (other than leftmost) into a new group
Actual Results: The tab 1 to the left of the actual tab that was pulled out gets closed in the current window. This means a tab gets completely lost.
e.g. You have tabs T1 T2 T3 T4 open. In Tab Sugar, pull tab T3 into a new group.
You end up with T1 T3 T4 left open in the current window. T2 gets lost.
If you drag the preview from the newly created group (pointing to T3) back into the original group, T3 will not reopen (nor would it anyway), but clicking on it will refer to the T3 that was incorrectly left open
Expected Results: The tab preview that is dragged out to create a new group should obviously correspond to the tab that is actually closed.
OS: Windows 7 Ultimate 64-bit
Chrome: 6.0.472.53
The text was updated successfully, but these errors were encountered: