Closed Bug 54367 Opened 25 years ago Closed 25 years ago

3-pane Focus ring is still slow

Categories

(SeaMonkey :: MailNews: Message Display, defect, P3)

x86
Linux
defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: alecf, Assigned: alecf)

Details

(Whiteboard: [rtm++]Fix in hand)

Attachments

(1 file)

FocusRingUpdate_Mail() takes .2 to .3 seconds on my machine even when the focus doesn't change, which is really bad. I hacked the JS and make it alot faster (0.001 seconds), patch on the way.
nominating for rtm putterman has reviewed this patch. It does not change the functionality of the focus ring in any way, it just makes it faster by fixing up comparisons in loops, simplifying logic, etc.
Status: NEW → ASSIGNED
Keywords: rtm
Whiteboard: Fix in hand
I second that nomination - this is an easy way to get a boost in mailnews performance.
QA Contact: esther → nbaca
rtm+, looks like a 200x or 300x improvement and we think that is a second or more on the target machine. The risk is low, worst case is focus rings fail to show up. Have r=putterman, looking for sr=mscott
Whiteboard: Fix in hand → [rtm+]Fix in hand
sr=mscott
PDT marking rtm++
Whiteboard: [rtm+]Fix in hand → [rtm++]Fix in hand
ok, fix went in (minus the timing stuff of course!)
oops, actually mark it fixed.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Don't we want this for the trunk too? I only saw a checkin on the branch, but I'm sure we want it fast even after Netscape's release of NS6.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
oh thanks, I almost forgot! I'll check in there today.
Status: REOPENED → ASSIGNED
fix finally checked into the trunk
oops, actually marking fixed.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago25 years ago
Resolution: --- → FIXED
Branch build 2000-10-06-10MN6: Linux 6.0 Fixed. Marking 'vtrunk' so this is checked on the trunk.
Keywords: vtrunk
marking vbranch.
Keywords: vbranch
I'm confused here. This was verified by nbaca on the branch on 10/9. the vtrunk keyword was added so that it would show up as needing verification on the Trunk. Then the vbranch keyword was added by varada (which implies that this has been Verified on the trunk and needs verification on the branch). I'm assuming varada's keyword was in error since it wasn't accompanied by build id and platforms tested. Removing vbranch keyword. BTW, how does one verify that this is fixed?
Keywords: vbranch
it's a code change, and I think we should just mark it verified... the problem was that clicking on a message took an absurdly long time because we were updating focus styles.
Status: RESOLVED → VERIFIED
OK, removing vtrunk keyword. This one is done :)
Keywords: vtrunk
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: