Communitay de Humptay
Lots of jibba jabba

Ctrl-W followed by Ctrl-Tab disables Last Tab plugin

rated by 0 users
Answered (Verified) This post has 1 verified answer | 3 Replies | 2 Followers

Top 50 Contributor
2 Posts
sakridge posted on Thu, Feb 25 2010 6:33 PM

I'm using Firefox 3.6 and Last Tab 2.2, when I press Ctrl-W and then without letting off the control key, press Ctrl-tab, the last tab plugin is disabled. After this the tab order reverts to linear and no tab selection popup is shown. Firefox still shows the plugin as enabled in the Tools -> Add ons menu.

Stephen

 

edit: platform is Windows XP SP 3

Answered (Verified) Verified Answer

Top 10 Contributor
592 Posts
Answered (Verified) Humpty replied on Fri, Feb 26 2010 9:08 PM
Verified by sakridge

Okay, I can confirm this happens. This is a bug with LastTab and related to how it tracks tabs. Given the uncommon conditions necessary to trigger this I'm not going to expend a lot of effort to fix it in LastTab 2.x; I will ensure it won't happen in the 3.x series.

All Replies

Top 10 Contributor
592 Posts
Humpty replied on Thu, Feb 25 2010 11:35 PM

Does LastTab work after you release the control key and try again?

In order to better work with other control key based tab navigation methods, such as say control-<digit>, LastTab temporarily disables tracking the active tab until the control key is released. The keyboard sequence you mention isn't exactly standard behavior: control-w, tab, tab, etc. Nevertheless control-w results in the active tab changing and so LastTab stops its tracking. Normally the control key would be released right after pressing control-w so the behavior you see would never happen.

Top 50 Contributor
2 Posts
No, it does not work again. Even after releasing control and then trying to tab again last tab is still disabled until I start a new browser session.
Top 10 Contributor
592 Posts
Answered (Verified) Humpty replied on Fri, Feb 26 2010 9:08 PM
Verified by sakridge

Okay, I can confirm this happens. This is a bug with LastTab and related to how it tracks tabs. Given the uncommon conditions necessary to trigger this I'm not going to expend a lot of effort to fix it in LastTab 2.x; I will ensure it won't happen in the 3.x series.

Page 1 of 1 (4 items) | RSS
Powered by Community Server (Non-Commercial Edition), by Telligent Systems