cancel
Showing results for 
Search instead for 
Did you mean: 

Cannot move or rearrange Tabs anymore - FF.17

Highlighted
New User

Cannot move or rearrange Tabs anymore - FF.17

I apologize if this has already been asked, but I cannot seem to find a recent reference to my problem so I'm filing this. Since the v17 upgrade, I can no longer rearrange my open tabs. It has the appearance of moving the tab (the ghost image) like before except that the "destination arrow" does not appear nor will the tab reposition itself. It worked perfectly in v16x and I have not installed any new add-ons so I'm guessing that it has to be something in v17.

8 REPLIES
Site Moderator

Re: Cannot move or rearrange Tabs anymore - FF.17

The Reset Firefox feature can fix many issues by restoring Firefox to its factory default state while saving your essential information. Note: This will cause you to lose any Extensions, Open websites, and some Preferences.

To Reset Firefox do the following:

  1. Go to Firefox > Help > Troubleshooting Information.
  2. Click the "Reset Firefox" button.
  3. Firefox will close and reset. After Firefox is done, it will show a window with the information that is imported. Click Finish.
  4. Firefox will open with all factory defaults applied.


Further information can be found in the Refresh Firefox - reset add-ons and settings article.

Did this fix your problems? Please report back to us!

New User

Re: Cannot move or rearrange Tabs anymore - FF.17

Because I also cannot rearrange my tabs, I followed these instructions, and have spent the last half hour working on restoring my workspace back to what works for me.

While reinstalling my add-ons, I have found that the add-on "bug489729" which prevents me from accidentally moving a tab to a new window -- a thing I do frequently because the gesture to do that in Firefox, click and pull down, is part of moving a tab -- is the cause of the problem, at least in my case.. I am reporting this to the maker of that addon and hope they can come up with an update. Time will tell which is more frustrating, having tabs unintentionally move to new windows or being unable to rearrange tabs.

New User

Re: Cannot move or rearrange Tabs anymore - FF.17

Spot on!! Removing the 'Bug48729' fix solved the problem - Thank you so much. But yeah, now we have to deal with the annoying "feature" that the fix cured. Here's hoping that the creator of the fix can get it to play nicely with v17. Or maybe it's not a problem/been removed in v17? One can only hope... Cheers & Thanks again!!

New User

Re: Cannot move or rearrange Tabs anymore - FF.17

I can confirm that the "tear off tab" still functions in FF17.

Others have already noted to the addon maker about the no-rearrange problem.

The "bug489729" add-on's info panel suggests an add-on "Undo Detach Tab" -- but an admin has made that one unavailable. Which stinks. On toast with jam.

Sigh. I just want to have my tabs NOT become new windows ...

New User

Re: Cannot move or rearrange Tabs anymore - FF.17

Well that's a bummer.

I haven't had it happen to me yet but the first time that I have a Tab open a new window, I may just reinstall the bug-fix. I hate not being able to re-arrange my Tabs, but the Detach Tab "feature" is intolerable! Lesser of the evils...

Cheers!

New User

Re: Cannot move or rearrange Tabs anymore - FF.17

The FF addons that move the tabs to the side (e.g. Vertical Tabs and Side Tabs) also block tab rearranging in FF17.

Both worked fine in FF16, so it's obviously something that Mozilla changed that's causing the problem.

New User

Re: Cannot move or rearrange Tabs anymore - FF.17

Tree Style tabs add-on solved my tabs not rearranging problem for those that prefer top to bottom tabs.

New User

Re: Cannot move or rearrange Tabs anymore - FF.17

I haven't updated this for a while but just to let anyone else having this problem know - the great 'White Alice0775' has updated the fix for FF17. (I'm not sure about v18 yet as I'm scared to update!!)

The bug fix is called "bug489729(Disable detach and tear off tab" v2.1

Whatever FF did in the v17 update screwed up the previous version of the fix but now that White Alice has updated the fix - it works perfectly again.

Let's just hope that v18+ doesn't mess it up again... Cheers!