Closed
Bug 74674
Opened 24 years ago
Closed 24 years ago
bad rows when switching from large to small (or empty) folder
Categories
(SeaMonkey :: MailNews: Message Display, defect, P1)
Tracking
(Not tracked)
VERIFIED
FIXED
mozilla0.9
People
(Reporter: sspitzer, Assigned: sspitzer)
References
Details
(Whiteboard: [nsbeta1+])
Attachments
(1 file)
652 bytes,
patch
|
Details | Diff | Splinter Review |
try this: load a large folder, scroll to the bottom. switch to a folder with a 5 messages. sometimes I see 10, with 5 blank bogus messages at the top load a large folder, scroll to the bottom. switch to a folder with a 0 messages. sometimes I crash fix for the crasher on the way, but I need to debug to figure out why this is happening.
Assignee | ||
Comment 1•24 years ago
|
||
we crash when we ask for the cell text at row "-8" I've got a patch for the crash, but I need to figure out why we ask for row -8 my guess is when I tell the outliner that the # of rows has changes, I'm giving the wrong value.
Status: NEW → ASSIGNED
Assignee | ||
Comment 2•24 years ago
|
||
crash = p1, 0.9
Priority: -- → P1
Target Milestone: --- → mozilla0.9
Assignee | ||
Comment 3•24 years ago
|
||
crasher is gone, bad row problem remains.
Summary: crash / problems when switching between folders → bad rows when switching from large to empty folder
Assignee | ||
Comment 4•24 years ago
|
||
doesn't happen when I'm scrolled to the top of the large folder. I'll tackle this tomorrow.
Summary: bad rows when switching from large to empty folder → bad rows when switching from large to small (or empty) folder
*** Bug 74817 has been marked as a duplicate of this bug. ***
Assignee | ||
Comment 6•24 years ago
|
||
I'm also seeing a bad row count if on startup if my inbox is small. I'll work on this today.
Comment 7•24 years ago
|
||
yeah, this doesn't look good! marking nsbeta1+
Keywords: nsbeta1
Whiteboard: [nsbeta1+]
Assignee | ||
Comment 8•24 years ago
|
||
fix in hand. I'll need a review from hyatt before I can check it in.
Assignee | ||
Comment 9•24 years ago
|
||
Comment 10•24 years ago
|
||
I don't buy this patch. Can you come by on Monday and explain the problem?
Assignee | ||
Comment 11•24 years ago
|
||
that patch makes more sense when you see it applied, than in patch form. the current code does this: if (mView) { // some stuff mView = nsnull; } if (mView) { // some other stuff. } "some other stuff" will never get reached. with the patch, we do this: if (mView) { // some stuff mView = nsnull; // some other stuff } if you need more explanation, I'll come down and talk to you about it on monday.
Assignee | ||
Comment 12•24 years ago
|
||
talked to hyatt, he's given the sr=.
Assignee | ||
Comment 13•24 years ago
|
||
fixed.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Comment 14•23 years ago
|
||
OK using apr17 commercial trunk build: linux rh6.2, mac OS 9.0, win98 no crash no bogus headers seen
Status: RESOLVED → VERIFIED
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•