Sök i support

Akta dig för supportbedrägerier: Vi kommer aldrig att be dig att ringa eller skicka ett sms till ett telefonnummer eller dela personlig information. Rapportera misstänkt aktivitet med alternativet "Rapportera missbruk".

Learn More

Search Bar magically resized and repositioned

  • 1 svar
  • 1 har detta problem
  • 20 visningar
  • Senaste svar av cor-el

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
Bifogade skärmdumpar

Alla svar (1)

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.