Closed
Bug 526716
Opened 15 years ago
Closed 15 years ago
When search box is on a full bookmarks toolbar, it shrinks to an unusable size.
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 447571
People
(Reporter: swaldman, Unassigned)
Details
Attachments
(1 file)
64.12 KB,
image/png
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2b1) Gecko/20091029 Firefox/3.6b1 (.NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2b1) Gecko/20091029 Firefox/3.6b1 (.NET CLR 3.5.30729)
In FF3.5, I suffered from the search box expanding and pushing all the bookmarks off the bar (bug 447571). This has been fixed in FF3.6beta1, but instead I now find that the search box is shrunk down to an unusable size.
I think that bug 408263 refers to a similar problem, but with the location bar. I'm not sure whether this should be considered a separate bug because it refers to the search box, or whether it should be added to 408263.
Reproducible: Always
Steps to Reproduce:
1. Place the search box on the bookmarks toolbar
2. Add enough bookmarks to the toolbar to more than fill it.
Actual Results:
Search box is too small to use.
Expected Results:
Search box should have a minimum width.
Reporter | ||
Comment 1•15 years ago
|
||
Note that although a theme is shown in this screenshot, I have tested with the default theme and the problem persists.
Reporter | ||
Comment 2•15 years ago
|
||
Upon further reading - this is *not* a dupe of 408263. 408263 refers to a problem with the size of the autocomplete dropdown of the location bar. This bug refers to the size of the search box itself, not the dropdown.
Updated•15 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → DUPLICATE
Reporter | ||
Comment 4•15 years ago
|
||
I do not believe that this is a dupe of 447571. That bug refers to the bookmarks being squeezed off in this situation, wheras this bug refers to the search box being squeezed into uselessness - exactly the opposite situation. I did not experience this bug in 3.5, but do in the 3.6 beta 1, and I suspect it is actually caused by the fix of 447571.
So, it is not a dupe of 447571. Having said this, comment #91 on 447571 may be relevant. It is also related to (but not exactly duplicating) 408263 and 448399. I'm not sure what your policy is on similar bugs, it may make sense to merge with one of these.
Thanks for your attention :-)
You need to log in
before you can comment on or make changes to this bug.
Description
•