Przeszukaj pomoc

Unikaj oszustw związanych z pomocą.Nigdy nie będziemy prosić Cię o dzwonienie na numer telefonu, wysyłanie SMS-ów ani o udostępnianie danych osobowych. Zgłoś podejrzaną aktywność, korzystając z opcji „Zgłoś nadużycie”.

Więcej informacji

Draging tabs to a new position in firefox 14 not working

  • 2 odpowiedzi
  • 3 osoby mają ten problem
  • 2 wyświetlenia
  • Ostatnia odpowiedź od digisnitch

more options

Today I noticed I could not drag tabs to a new position (the feature where you can click and hold on a tab, and drag it to a different position on the tab bar, new window, etc.)

I have started in safe mode and the issue continued, so it seems unlikely to be caused by and addon.

I'm confused as this feature was working yesterday and I have not changed anything

Today I noticed I could not drag tabs to a new position (the feature where you can click and hold on a tab, and drag it to a different position on the tab bar, new window, etc.) I have started in safe mode and the issue continued, so it seems unlikely to be caused by and addon. I'm confused as this feature was working yesterday and I have not changed anything

Wybrane rozwiązanie

@jscher2000, lol thank you for trying

After further investigation I found I couldn't drag ANYTHING. At a loss I thought I'd try restarting my system as a restart was the only difference from yesterday, and the feature now seems to be working...no idea what could have happened, but it's fixed now.

I really should know better than to not trying a restart to correct an issue.

Przeczytaj tę odpowiedź w całym kontekście 👍 1

Wszystkie odpowiedzi (2)

more options

Misread post, never mind!

Zmodyfikowany przez jscher2000 - Support Volunteer w dniu

more options

Wybrane rozwiązanie

@jscher2000, lol thank you for trying

After further investigation I found I couldn't drag ANYTHING. At a loss I thought I'd try restarting my system as a restart was the only difference from yesterday, and the feature now seems to be working...no idea what could have happened, but it's fixed now.

I really should know better than to not trying a restart to correct an issue.