Avatar for Username

Mozilla 도움말 검색

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

자세히 살펴보기

이 쓰레드는 보존되었습니다. 만약 도움이 필요하시면 새로운 질문을 올려주세요.

Search Bar magically resized and repositioned

  • 1 답장
  • 1 이 문제를 만남
  • 4 보기
  • 최종 답변자: cor-el

stormcloud2030
stormcloud2030
more options

Hi,

Firefox version 110.0.1 (64-bit) for Windows 11 has decided to change it's layout to something I don't like and I can't get it to change back. I've attached a picture of what it currently looks like to this ticket.

What it should be have is a Search Bar that is right aligned (as you can see it's left aligned) and it should be wide enough to almost fill the width of the browser - (I'd like to add some buttons to the right of the search bar)

I've tried clicking on the Vent Icon -> More Tools -> Customise Tool Bar to fix this but I can't make the Search Bar either align right or stretch

Hi, Firefox version 110.0.1 (64-bit) for Windows 11 has decided to change it's layout to something I don't like and I can't get it to change back. I've attached a picture of what it currently looks like to this ticket. What it should be have is a Search Bar that is right aligned (as you can see it's left aligned) and it should be wide enough to almost fill the width of the browser - (I'd like to add some buttons to the right of the search bar) I've tried clicking on the Vent Icon -> More Tools -> Customise Tool Bar to fix this but I can't make the Search Bar either align right or stretch
첨부된 스크린샷

모든 댓글 (1)

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

That happens if you have placed the search bar on the Bookmarks Toolbar and had removed the "Bookmarks Toolbar Items" control from the toolbar. In Firefox 110 this causes to get a large empty space at the left end and the items you placed on the toolbar get pushed to the right. You can re-add the "Bookmarks Toolbar Items" at the far right (after all buttons you added) via customize mode and remove possible bookmarks.

This issue is handled in bug 1819980 and has been fixed in 112 and has been approved for 111 as well.