User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:18.104.22.168) Gecko/20090715 Firefox/3.5.1 (.NET CLR 3.5.30729) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:22.214.171.124) Gecko/20090715 Firefox/3.5.1 (.NET CLR 3.5.30729) Everytime when I start Firefox the Search Bar(see URL) maximize. So that I can't see much Bookmarks in this bar. Only about 1 or 2. Only when I go to the settings, therefor right clicking on the toolbar, and chose costumize. After closing it without changing anything the Search Bar minimize so that a maximum of bookmarks are show up. This problem appears at any window size and fullscreen. I already tried: Search the problem on google. Search at the settings. Trying to reinstall firefox. Reproducible: Always Steps to Reproduce: 1.Open firefox 2.Look at the Bookmarks-toolbar while the search bar is included in it. Actual Results: The Search bar maximize its size a lot so that most of the bookmarks will be push out of the line. Expected Results: It should only make the search bar so big as its usefull and not so huge that its pushing out the bookmarks. Theme: NASA Night Launch 0.6.2xxxx (up-to-date) Screen resolution: 1280x1024 Windows XP Prof. SP3
This may actually be the "Bookmarks collapse when on the same bar as other things" bug 447571. If you find that the search bar doesn't do this when the bookmarks are on their own bar, please dupe this bug to that.
Version: 3.5 Branch → unspecified
Reporter, are you still seeing this issue with Firefox 3.6.13 or later in safe mode or a fresh profile? If not, please close. These links can help you in your testing. http://support.mozilla.com/kb/Safe+Mode http://support.mozilla.com/kb/Managing+profiles
Whiteboard: [CLOSEME 2011-2-25]
This bug has had the CLOSEME tag for several weeks and the date in the tag is far gone. If the reporter can still see this issue, Please retest with Firefox 3.6.x or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). Then please remove the closeme tag in the whiteboard, mark the bug against the proper version and comment on the bug.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.