Why does a user have to lose the ability to scroll tabs in backward
order if he likes the "Tab Previews" feature?
I suggest to back out <a href="https://bugzilla.mozilla.org/
show_bug.cgi?id=669265">bug 669265</a> and set another hotkey for it,
like "CTRL+SHIFT+`".
Because with browser.ctrlTab.previews=true, you go through tabs in
most-recently-used order. The opposite direction of this isn't useful.
> I suggest to back out<a href="https://bugzilla.mozilla.org/
> show_bug.cgi?id=669265">bug 669265</a> and set another hotkey for it,
> like "CTRL+SHIFT+`".
That bug didn't change the fact that CTRL+SHIFT+TAB didn't take you to
the "previous tab" with browser.ctrlTab.previews=true.
To be fair: IIUC, that's exactly the same as how Alt+Tab works for window
management (and people still find the "Shift" order-reversal useful there).
(That is to say -- Alt-Tab goes through windows in most-recently-used
order, at least on Ubuntu, and the Shift modifier reverses the direction.)
Yeah, on Windows too, and it's useful when you overshoot while changing.
Mike
The original mail only applies to holding Shift from the beginning when
hitting Ctrl+Tab. If you hit Ctrl+Tab, release Tab, hold Shift in
addition to Ctrl and hit Tab again, you do go back in the list.
And what if a user has browser.ctrlTab.recentlyUsedLimit set to 0?
Then there is no most-recently-used order, but CTRL+SHIFT+TAB still
occupies that hotkey.
So your reasoning can be hardly applied here.
> > I suggest to back out<a href="https://bugzilla.mozilla.org/
> > show_bug.cgi?id=669265">bug 669265</a> and set another hotkey for it,
> > like "CTRL+SHIFT+`".
>
> That bug didn't change the fact that CTRL+SHIFT+TAB didn't take you to
> the "previous tab" with browser.ctrlTab.previews=true.
Okay, maybe that was broken even earlier, or just no one thought that
a user may have
browser.ctrlTab.recentlyUsedLimit set to 0
I suggest that you set browser.ctrlTab.previews to false. The main point
of the previews panel is the most-recently-used sorting.
I already proved you that this is wrong: we have a nice pref
browser.ctrlTab.recentlyUsedLimit which changes that order, in case it
is set to 0.
So your explanation doesn't work here and you should think over re-
binding the key for Tab Previews from CTRL+SHIFT+TAB to another hotkey.
It's a hidden pref and I added it. Its existence doesn't really mandate
anything.