Mozilla 도움말 검색

고객 지원 사기를 피하세요. 저희는 여러분께 절대로 전화를 걸거나 문자를 보내거나 개인 정보를 공유하도록 요청하지 않습니다. "악용 사례 신고"옵션을 사용하여 의심스러운 활동을 신고해 주세요.

자세히 살펴보기

I can no longer drag tabs to a different position.

  • 3 답장
  • 1 이 문제를 만남
  • 1 보기
  • 최종 답변자: Taxlady

more options

I recently updated to version 80.0 and now I can't drag the tabs to a new position. I also can't drag a tab down to open it in a new window. Is there something I need to do differently now?

I recently updated to version 80.0 and now I can't drag the tabs to a new position. I also can't drag a tab down to open it in a new window. Is there something I need to do differently now?

선택된 해결법

Thank you both for your replies. I had a stressful week, or I would have gotten back to this sooner. It may have been a Windows problem. It spontaneously went away when Win 10 did an update.

문맥에 따라 이 답변을 읽어주세요 👍 0

모든 댓글 (3)

more options

Hi Taxlady, you should still be able to rearrange tabs by dragging, and also to "tear off"/"detach" tabs to their own window.

There is a recently added preference related to detaching tabs that could disable that second function. You can check here:

(1) In a new tab, type or paste about:config in the address bar and press Enter/Return. Click the button accepting the risk.

(2) In the search box in the page, type or paste detach and pause while the list is filtered

(3) If the browser.tabs.allowTabDetach preference is bolded and has a value of false, double-click it to restore the default value of true

More info on about:config: Configuration Editor for Firefox.

more options

Start Firefox in Safe Mode to check if one of the extensions ("3-bar" menu button or Tools -> Add-ons -> Extensions) or if hardware acceleration or userChrome.css is causing the problem.

  • switch to the DEFAULT theme: "3-bar" menu button or Tools -> Add-ons -> Themes
  • do NOT click the "Refresh Firefox" button on the Safe Mode start window
more options

선택된 해결법

Thank you both for your replies. I had a stressful week, or I would have gotten back to this sooner. It may have been a Windows problem. It spontaneously went away when Win 10 did an update.