editor should use a single parser instance

RESOLVED INCOMPLETE

Status

()

Core
Editor
P3
minor
RESOLVED INCOMPLETE
19 years ago
8 years ago

People

(Reporter: buster, Assigned: Akkana Peck)

Tracking

({perf})

Trunk
Future
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

19 years ago
Today, we instantiate a new parser instance every time we output content from
the editor.  It would be much more efficient to just reuse a single parser
instance, probably even a static instance shared by all editors.  When bug 8609
is fixed, we can switch over to doing this.
(Reporter)

Updated

19 years ago
Depends on: 8609
Target Milestone: M15
(Assignee)

Updated

19 years ago
Status: NEW → ASSIGNED
(Assignee)

Updated

19 years ago
Status: ASSIGNED → RESOLVED
Last Resolved: 19 years ago
Resolution: --- → REMIND
(Assignee)

Comment 1

19 years ago
The bug this depends on was just resolved/remind, and this one can't be done
until that one is fixed; marking this one resolve/remind too.

Comment 2

18 years ago
reopening and marking Future...
Status: RESOLVED → REOPENED
Resolution: REMIND → ---
Target Milestone: M15 → Future
(Assignee)

Comment 3

18 years ago
The bug this depends on is still open, so this is still future.
Status: REOPENED → ASSIGNED
OS: Windows NT → All
Hardware: PC → All

Updated

17 years ago
Whiteboard: [eperf]

Comment 4

17 years ago
spam composer change
Component: Editor: Core → Editor: Composer
(Assignee)

Updated

17 years ago
Component: Editor: Composer → Editor: Core
QA Contact: sujay → editor

Updated

8 years ago
Keywords: perf

Updated

8 years ago
Whiteboard: [eperf]

Updated

8 years ago
URL: N/A

Comment 5

8 years ago
This is no longer relevant...
Status: ASSIGNED → RESOLVED
Last Resolved: 19 years ago8 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.