Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Pomoc přepytać

Hladajće so wobšudstwa pomocy. Njenamołwimy was ženje, telefonowe čisło zawołać, SMS pósłać abo wosobinske informacije přeradźić. Prošu zdźělće podhladnu aktiwitu z pomocu nastajenja „Znjewužiwanje zdźělić“.

Dalše informacije

Draging tabs to a new position in firefox 14 not working

  • 2 wotmołwje
  • 3 maja tutón problem
  • 83 napohladow
  • Poslednja wotmołwa wot digisnitch

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

Wubrane rozrisanje

@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.

Tutu wotmołwu w konteksće čitać 👍 1

Wšě wotmołwy (2)

Misread post, never mind!

Wot jscher2000 - Support Volunteer změnjeny

Wubrane rozrisanje

@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.