<html><head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"></head><body
bgcolor="#FFFFFF" text="#000000">
I was going to post these using the Feedback component instead of here,
but that component does not give enough room to actually describe an
issue, so it's not very helpful. Hmm, I guess that means I'm posting
three issues - that one, and these two:<br>
<br>
1. When Firefox launches, it seems to show all tabs, regardless of tab
groupings. The user must then go into the tab groups page and select a
group to filter the tab list. I think that when Firefox launches, it
should automatically load the previous tab group and filter accordingly.
Of course, this applies when it's set to load tabs from last time.<br>
<br>
2. When displaying the tab groups page, if the user drags a tab from a
stack in one group to another group, the source group should now show
the same tab that would have been shown had the user closed the tab that
was moved. Instead, it jumps to the first tab in that stack. Also,
closing the tab groups page now acts as if the destination group had
been selected. This makes it very difficult to move several adjacent
tabs from one group to another, if the source group is displayed as a
stack instead of a grid.<br>
<br>
For example, if I have 5 tabs at the "end" of a tab group, one of which
is the current tab before going to the tab groups page, and these tabs
are displayed in a stack (because the group has many other tabs) and I
want to drag all 5 to another group, the process is as follows:<br>
<ol>
<li>Drag displayed tab from source group to destination group.
Source group stack now shows first tab of group (whereas I think it
should show the adjacent tab, mirroring the behavior of tab selection
when closing a tab).</li>
<li>Select source tab group. (Pressing "Escape" doesn't revert to
the previously selected group, it follows the moved tab to the
destination group.)</li>
<li>Select the desired tab at the end of the list, which is the tab
that would have been selected had I closed instead of moved the previous
tab.</li>
<li>Re-display the tab groups screen, which now shows the selected
tab at the top of the stack for the current group.</li>
<li>Repeat steps 1 through 5 four more times.<br>
</li>
</ol>
But, I think the process should be as follows:<br>
<ol>
<span><li>Drag displayed tab from source group to destination group.
Source group stack now shows the adjacent tab to the one just moved.</li>
<li>Repeat step 1 four more times.<br>
</li></span>
</ol>
<br>
Ever since the decision was made to de-couple tab groups from a pinned
app tab, the workflow in general for managing the groups has been a lot
more cumbersome than I'd gotten used to. These particular issues cause
me a great deal of extra work daily, and I think that the current
workflow is inconsistent with what a typical user would expect, so I'd
really love to see them corrected!<br>
<br>
If the above is a bit tricky to visualize, I believe I can whip up a
small, quick screen cap video to demonstrate the issue.<br>
<br>
<div class="moz-signature">-- <br><hr>
<p>
Adam Yarnott<br>
Blue Ninja Software<br>
<a href="http://www.BlueNinjaSoftware.com">www.BlueNinjaSoftware.com</a>
</p>
</div>
</body>
</html>