58346 - Tree columns in multiple search results window get out-of-sync

Status: VERIFIED WORKSFORME

(SeaMonkey :: Search, defect, P3)

Description

[Blake Ross]

Build ID: new branch / trunk

Steps to Reproduce:

(1) Search | My Sidebar Search Tab > Advanced
(2) Open the My Sidebar Search tab
(3) Choose "All Engines" in the dropdown next to "within"
(4) Check off more than 1 search engine in the list
(5) Search for something, e.g. `test'
(6) In the search results window that appears in the content area, drag the 
horizontal splitter upwards until a scrollbar is needed to scroll the results.
(7) Scroll up and down with the scrollbar

Result: The columns get out of sync.  Same as in bug 55899.

Comment 1

[Eric Vaughan]

To fix give each column in the tree a width. Pick anything like give each column
a width say "width: 20px".

Comment 2

[Eric Vaughan]

The fix is described in my last comment.

Comment 3

[Blake Ross]

okay.

Comment 4

[Blake Ross]

Attachment: patch

Comment 5

[Eric Vaughan]

Close but in line style is kind of a no no in XUL files. Each of these columns
has IDs so you will probably want to go into the CSS files for them and set
their widths there. 

Comment 6

[Blake Ross]

I realize that (i'm the skinability QA :-), but it seems very bad to fix this in 
the css -- because then any skin authors who aren't aware that you need to 
specify with are going to encounter this problem.  This seems like the kind of 
thing that needs to be fixed in all skins, hence the reason I put it in the xul. 
 And I was under the impression that skin authors could override this with 
!important in the CSS.  Is that not the case?

Comment 7

[Blake Ross]

Hm, upon further thought, I suppose not.  So how do you suggest fixing this?  
Fixing it in the CSS still seems risky to me.  But if it's the only way...

Comment 8

[Eric Vaughan]

I believe there are global skin files and Skins are then build on top of them.
Ben should be able to tell you exactly what CSS files to place these fixes in.
CCing Ben. 

Comment 9

[Blake Ross]

Ben/Eric: any word on this?

Comment 10

[Blake Ross]

Hyatt, what do you think...?

Comment 11

[Marcia Knous [:marcia]]

Netscape nav triage team: as per Matt Fisher's pre-triage recommendation, this 
bug is nsbeta1-.

Comment 12

[Asa Dotzler [:asa]]

Sorry for the spam, I just wanted to follow knous's comment with a
clarification.  nsbeta1- keyword means that Netscape management has decided that
it will not be able to contribute resources to fixing this for the next Netscape
release.  It does not mean that a fix for this would not be accepted.  Normal r=
and sr= checkin procedure still applies.

Comment 13

[Blake Ross]

WFM, this should become outliner anyways.

Comment 14

[sairuh (rarely reading bugmail)]

mass-verifying WorksForMe bugs which haven't changed since 2001.12.31.

set your search string in mail to "EmperorLondoMollari" to filter out these
messages.