228395 - search box displaying incorrectly, shorter, to the left, blank space on the right

Status: RESOLVED WORKSFORME

(Firefox :: Search, enhancement)

Description

[kinabrew]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.6b) Gecko/20031213 Firebird/0.7+
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.6b) Gecko/20031213 Firebird/0.7+

In previous versions of Firebird, I was able to modify userChrome.css to make
the search box wider. Now, if I do this, the search box just appears moved to
the right. The available space to type in is increased, but it doesn't draw
correctly.

Reproducible: Always

Steps to Reproduce:
1.Customize toolbar and move the search box to be next to the bookmarks. Quit
Firebird.
2.Add the following to userChrome.css:
/* Make the Search box flex wider */
#search-container {
   -moz-box-flex: 1.75 !important;
}
3.Launch Firebird, and type a sentence which is longer than the search box.
Actual Results:  
The search box appears to have been moved over to the left, and text spills out
of the right side of the search box.

Expected Results:  
The width of the search box should have been visibly expanded.

Comment 1

[Steven Garrity [:sgarrity]]

Confirming on Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8a)
Gecko/20040417 Firefox/0.8.0+

Perhaps a pinstripe-theme issue?

Comment 2

[Asaf Romano (gone)]

*** Bug 267831 has been marked as a duplicate of this bug. ***

Comment 3

[:Gavin Sharp [email: [e-mail]]]

Matt, is this still an issue in recent builds? Anyone else seeing this?

Comment 4

[Kevin Gerich]

Should still be an issue. At least I didn't fix it. Patches welcome :)

Comment 5

[mitchgould]

I really would like to see the Search Box wider. The address box could
definitely be scaled back to make more room for it.

Comment 6

[:Gavin Sharp [email: [e-mail]]]

Think this bug probably isn't very relevant now, especially in light of bug 205011.

Comment 7

[nrlz]

(In reply to comment #6)
> Think this bug probably isn't very relevant now, especially in light of bug
> 205011.
> 

Ironically it was the workaround for bug 205011, which motivated this bug.