Closed
Bug 117612
Opened 23 years ago
Closed 15 years ago
Search text field in the sidebar tab, with the "basic" pref, is too long and hides search button.
Categories
(SeaMonkey :: Search, defect)
SeaMonkey
Search
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: dales, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: polish, Whiteboard: [adt3])
Attachments
(3 files)
70.17 KB,
image/jpeg
|
Details | |
77.97 KB,
image/jpeg
|
Details | |
707 bytes,
patch
|
Details | Diff | Splinter Review |
I am running the Mozilla Build 2001123108 (Mac) build curenly, but this problem has been present in every Mac build for a long time. The text field in the Search sidebar tab fails to shrink enough to show the search button (or even a piece of it). At the present time I am in a Mac OS 9.1 system running at 800x600 resolution. 1. The sidebar's right edge is aligned with the "Reload" button on the Navigation toolbar. I can not see either any part of the search button or the popup arrow on the "using" popup menu. There is no scrollbar visible in the search results window either. (I'm going to attach a screenshot showing the state.) 2. If I drag the sidebar open to the ~40% of window width mark (as I will show in my second attached screenshot), I have reach the point where the full width of the scrollbar is just visible and the search button and full width of the popup menu are visible. 3. This is not required on Mac OS X builds (nor so far as I can recall on WinNT builds.) On those the text filed shrinks down to a minimum size that is small enough to permit a portion of the Search button to be seen even when the sidebar width is aligned with the "Reload" button. The failure in that state to display the full width of the popup doesn't prevent it from being used.
Although I call this "full" width, it is really not the maximum width permitted to the sidebar, which is about midscreenb, but the width just sufficient to show the full width of the scrollbar. It appears that this is determined by the width of the popup menu. If expanded further, the text field expands to fill the space left by the Search button as it follows the dragbar. I should mention again that this is with the Sidebar Search preferences set to display "Basic", which will be the default and thus have maxiumum vvisibility to users.
--> search/claudius
Component: Sidebar → Search
QA Contact: sujay → claudius
Comment 4•23 years ago
|
||
I see this on Win2K as well. CC'ing hewitt for suggestions on how to fix this.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: polish
Priority: -- → P2
Target Milestone: --- → mozilla0.9.8
Updated•23 years ago
|
Target Milestone: mozilla0.9.8 → mozilla0.9.9
Comment 5•23 years ago
|
||
Search triage team: nsbeta1+
Comment 6•23 years ago
|
||
Removed "flex" attribute from textbox.
Updated•23 years ago
|
OS: Mac System 9.x → All
Hardware: Macintosh → All
Comment 7•22 years ago
|
||
Koike, The above patch doesn't fix the problem for me.
Comment 8•22 years ago
|
||
Reassigning 'several bugs at once' to Steve Morse, to level the load better across the team.
Assignee: sgehani → morse
Updated•22 years ago
|
Whiteboard: [adt3]
springs (or the XUL 1.0 equivalent) need to be placed around the widgets in the box, so that they will center as the sidebar is changed. See me if you need help.
Comment 10•22 years ago
|
||
Mass moving nsbeta1+/adt3 bugs assigned to Navigator team engineers out to target milestone 1.0.1. Please confine your attentions to driving down our list of TM 1.0 bugs for beta. Better to help, debug, or test one of them than fix one of these.
Target Milestone: mozilla1.0 → mozilla1.0.1
Comment 11•22 years ago
|
||
Changing nsbeta1+ [adt3] bugs to nsbeta1- on behalf of the adt. If you have any questions about this, please email adt@netscape.com. You can search for "changing adt3 bugs" to quickly find and delete these bug mails.
Keywords: nsbeta1-
Comment 12•22 years ago
|
||
Changing nsbeta1+ [adt3] bugs to nsbeta1- on behalf of the adt. If you have any questions about this, please email adt@netscape.com. You can search for "changing adt3 bugs" to quickly find and delete these bug mails.
Keywords: nsbeta1+
Updated•22 years ago
|
Status: NEW → ASSIGNED
Target Milestone: mozilla1.0.1 → mozilla1.1alpha
Comment 13•22 years ago
|
||
reassign to component owner
Assignee: morse → sgehani
Status: ASSIGNED → NEW
Comment 14•22 years ago
|
||
*** Bug 115882 has been marked as a duplicate of this bug. ***
Comment 15•22 years ago
|
||
http://bugzilla.mozilla.org/show_bug.cgi?id=152430 May also be a duplicate of this bug. A work around for this problem is to delete or rename any search plugin with a long name. For example I often use the a search plugin for w3c.org. The plugin name is "World Wide Web Consortium" When ever I use this plugin it pushes my "next" and "search" buttons off the viewable area of my sidebar when it is aligned with the "reload" button. Removing the plugin or renaming the <search name=""> in the plugin to something shorter fixes the problem.
Updated•22 years ago
|
Comment 16•22 years ago
|
||
*** Bug 71532 has been marked as a duplicate of this bug. ***
Comment 17•22 years ago
|
||
*** Bug 152430 has been marked as a duplicate of this bug. ***
Assignee | ||
Updated•16 years ago
|
Product: Core → SeaMonkey
Updated•16 years ago
|
Assignee: samir_bugzilla → nobody
Priority: P3 → --
QA Contact: claudius → search
Target Milestone: Future → ---
Comment 19•15 years ago
|
||
MASS-CHANGE: This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
Reporter | ||
Comment 20•15 years ago
|
||
As submitter of this bug, I have checked on the current version of SeaMonkey. There are some differences ... I am now running with Mac OS X 10.4.11 (Tiger), not Mac OS 9.1. On Mac OS X it WORKs-FOR-ME now.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•