typing optimization needs to be implemented

VERIFIED WONTFIX

Status

()

Core
Editor
P3
normal
VERIFIED WONTFIX
19 years ago
17 years ago

People

(Reporter: sujay, Assigned: Simon Fraser)

Tracking

({helpwanted, perf, pp})

Trunk
Future
helpwanted, perf, pp
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

19 years ago
using 5/11 build of apprunner.

The following functionality needs to be implemented for editor

typing optimzation for Mac, Windows and Linux

Updated

19 years ago
Assignee: kostello → sfraser
Target Milestone: M9

Comment 1

19 years ago
Reassign to Simon Fraser, setting milestone to M9

Updated

19 years ago
Blocks: 10770
(Assignee)

Updated

19 years ago
Status: NEW → ASSIGNED
Target Milestone: M9 → M10
(Assignee)

Comment 2

19 years ago
Ain't gonna happen for M9.
(Assignee)

Updated

19 years ago
Target Milestone: M10 → M13
(Assignee)

Comment 3

19 years ago
M13
(Assignee)

Updated

19 years ago
Target Milestone: M13 → M15
(Assignee)

Comment 4

19 years ago
Perf tuning, not clear if we'll even need it. M15.

Comment 5

18 years ago
moving to m17
Target Milestone: M15 → M17

Comment 6

18 years ago
this is performance work not a feature, removing feature keyword
Keywords: pp
Summary: (feature) typing optimization needs to be implemented → typing optimization needs to be implemented

Updated

18 years ago
Keywords: perf

Comment 7

18 years ago
moving out to m20
Target Milestone: M17 → M20

Comment 8

18 years ago
moving this to m19 with other perf bugs
No longer blocks: 10770
Target Milestone: M20 → M19

Comment 9

18 years ago
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

Comment 10

18 years ago
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.
(Assignee)

Comment 11

18 years ago
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.

Comment 12

18 years ago
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...
(Assignee)

Comment 13

18 years ago
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.

Updated

18 years ago
Blocks: 50440

Updated

18 years ago
Blocks: 51233

Comment 14

18 years ago
moving to future, per review with bij and beppe
Keywords: helpwanted
Target Milestone: M19 → Future

Comment 15

18 years ago
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.
(Assignee)

Comment 16

18 years ago
I agree that it's not obvious this optimization will be useful/safe.
Status: ASSIGNED → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → WONTFIX
(Reporter)

Comment 17

18 years ago
verified in 9/20 build.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.