When the add-on's sidebar opens with only one tab in the browser, the tab will properly mark as active. However when another tab is opened or activated the original tab will not get the .active class removed from it unless it is selected again. Therefore there is some problem either with the way the original tab is activated (using the vtt clear, vtt init, vtt activate loop-cycle), the tab's deactivation or the new tab's activation.
The same problem does not occur when two or more tabs are open in the browser before the sidebar is opened.
P.S.:First appeared on 582531e, which is when the code for tab activation/deactivation events first appeared.
When the add-on's sidebar opens with only one tab in the browser, the tab will properly mark as active. However when another tab is opened or activated the original tab will not get the
.active
class removed from it unless it is selected again. Therefore there is some problem either with the way the original tab is activated (using thevtt clear, vtt init, vtt activate
loop-cycle), the tab's deactivation or the new tab's activation.The same problem does not occur when two or more tabs are open in the browser before the sidebar is opened.
P.S.:First appeared on 582531e, which is when the code for tab activation/deactivation events first appeared.