Closed
Bug 815734
Opened 12 years ago
Closed 11 years ago
Thunderbird search jumps up higher when clicking "More"
Categories
(Thunderbird :: Search, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 731612
People
(Reporter: firstpeterfourten, Unassigned)
Details
When I conduct a global search for a term across my IMAP accounts (that have plenty of folders each) and get several results, there is a "More" button on the bottom that will show additional results beyond those originally shown. As of a few versions ago, the list expanded when clicking More instead of paginating. However, in addition to displaying more, it also jumps the vertical scroll to a much higher position. It has done this consistently *and does this in safe mode.* The higher position is deterministic and is the same on the first click of "More" or the tenth, and it depends on the vertical height of the window (neither the top nor bottom are constant across different vertical window sizes) but I can't find an obvious pattern about where it jumps to. It is very disorienting to have to scroll down and figure out which of the results you've already looked through to discover the boundary where you should keep searching, and then do it again after each press of "More." It seems like this bug ought to have several dupes in here by now, given how reliably it happens for me and how annoying it is, but again I haven't found a good one that describes this issue. It seems to my foggy memory that this has been happening ever since the update that made the list expand instead of paginate. Any ideas what it might be aligning to or how to get it to stop? The desired behavior is that when I click "More," the top of the scroll remains just where it is, and new content appears on the bottom, extending the scroll range down.
This seems to be a duplicate of Bug 731612
Comment 2•11 years ago
|
||
(In reply to pysmah from comment #1) > This seems to be a duplicate of Bug 731612 good catch
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•