Closed Bug 12420 Opened 26 years ago Closed 25 years ago

Performance improvements to IME text range handling

Categories

(Core :: Internationalization, defect, P3)

Product:
Core
Component:
Internationalization
Type:
defect

Tracking

()

Status:
VERIFIED WONTFIX

People

(Reporter: tague, Assigned: shanjian)

References

Details

(Keywords: intl, perf)

there are some simple performance improvements that can be done to IME text range handling once persistence is implemented for nsGUI events. when nsGUIEvent's can persist after dispatch, we can avoid alot of the duplication of the nsGUIEvent form of the text events into the nsPrivateDOMTextEvent form.
Status: NEW → ASSIGNED
Target Milestone: M15
Whiteboard: [Perf]
Putting on [Perf] radar.
update [per waterson@netscape.com's email], the performance work on IME editing should wait until after some optimizations on DOM events are completed. no point in doing everything twice.
Blocks: 16127
Is there a bug to track "optimizations on DOM events" that we can make this bug depend upon?
bulk reassign bugs to ftang for now
Status: NEW → ASSIGNED
Keywords: perf
Bulk add of "perf" to new keyword field. This will replace the [PERF] we were using in the Status Summary field.
not sure what this bug is all about. have we done the "optimization to DOM events" that tague is talking about? (I have no recollection of the email he mentions.)
Whiteboard: [Perf]
Target Milestone: M15 → M19
Move it to M19
IME bug which no one know what it really mean now. REassign to shanjian
Assignee: ftang → shanjian
Status: ASSIGNED → NEW
Status: NEW → ASSIGNED
Keywords: intl
do not know what this bug is talking about. If there issue raised again IME, we can fix the problem there.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → WONTFIX
Verified as Wontfix.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.