There's a rule I use when programming: "While the user is making a change, they should see the result of that change while they are making it." This rule is used throughout GNOME and should apply to tab movement as well as document editing.
I personally don't see how the arrows allows for more precision. After all, what could be more precise than seeing the tab in its desired position as you move it? Of course dragging tabs between windows is important, so if that function is at risk by all means leave the code as is.
This is just one of the three problems. I don't see how problems 1 and 2 can be difficuilt to fix.
There's a rule I use when programming: "While the user is making a change, they should see the result of that change while they are making it." This rule is used throughout GNOME and should apply to tab movement as well as document editing.
I personally don't see how the arrows allows for more precision. After all, what could be more precise than seeing the tab in its desired position as you move it? Of course dragging tabs between windows is important, so if that function is at risk by all means leave the code as is.
This is just one of the three problems. I don't see how problems 1 and 2 can be difficuilt to fix.