using 5/11 build of apprunner. The following functionality needs to be implemented for editor typing optimzation for Mac, Windows and Linux
Reassign to Simon Fraser, setting milestone to M9
Ain't gonna happen for M9.
Perf tuning, not clear if we'll even need it. M15.
moving to m17
Target Milestone: M15 → M17
this is performance work not a feature, removing feature keyword
Summary: (feature) typing optimization needs to be implemented → typing optimization needs to be implemented
moving out to m20
Target Milestone: M17 → M20
moving this to m19 with other perf bugs
No longer blocks: 10770
Target Milestone: M20 → M19
please do not nominate for nsbeta3 -- this will be addressed after crashes, regressions, correctness and polish bugs have been resolved, all Composer perf bugs have been set to m19/m20
Can somebody confirm whether or not this is a dup of 47395 [nsbeta3+] (or vice-versa)? Trying to consolidate typing/keypress related performance issues and fix them myself.
This bug was filed preemptively a long time ago, to migrate to Mozilla a key handling optimization that was present in 4.x. It's separate from 47395.
sfraser: can you point me at the optimization you had in mind? i'm charged with fixing bug 47395, and if the optimization applies to that, my job will be easier; or alternately, i can fix 47395 and close this bug as a dup...
The aim of this bug was to implement a key handling optimization that was in 4.x, which was to look ahead in the native event queue for key presses, and handle them all at one time. It it not clear to me that we need this optimization in Mozilla. It should be treated independently of 47395.
moving to future, per review with bij and beppe
Target Milestone: M19 → Future
the fix of handling all keypress events in the native queue could cause problems with event sequencing... saari would probably cringe, anyway :) ... considering the other optimizations we've done, i suggest resolving this as WONTFIX. see 48758 for current work.
I agree that it's not obvious this optimization will be useful/safe.
Status: ASSIGNED → RESOLVED
Last Resolved: 19 years ago
Resolution: --- → WONTFIX
verified in 9/20 build.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.