Closed enko closed 4 years ago
Is it a bug or this is simply controled by pref browser.tabs.insertAfterCurrent
Can you go into about:config
and check the value of browser.tabs.insertAfterCurrent
?
It's a bug in the category of why did you even do that
.
browser.tabs.insertAfterCurrent
is a good hint, with the bug fixed one then can probably control the behavior to their liking.
But... here (FF v73, Win10) I cannot reproduce, but I can control with browser.tabs.insertAfterCurrent
... that is why I am confused.
It's about the keyboard shortcut Alt+X.
But OP is saying
when I'm pressing ctrl+t
Here is my video of ctrl+t behavior: https://www.dropbox.com/s/sw2mcgq2b4l0ane/newtab.mp4?dl=0
OP is expecting Alt+X to behave the same way as Ctrl+T.
Fixed in just published v1.8
Actual behavior
Use the keyboard shortcut for opening a new tab from the same container as the current container. The new tab will be next to the current tab.
See this video:
Expected behavior
I would expect the new tab to be at the end of the tab list, like when I'm pressing
ctrl+t
.Steps to reproduce
Select a tab that it not at the end and press the shortcut to open a new tab of the current container.