Closed
Bug 74914
Opened 24 years ago
Closed 2 years ago
Remove unneeded editor postprocessing for mailcitre insertion
Categories
(Core :: DOM: Editor, defect, P3)
Core
DOM: Editor
Tracking
()
RESOLVED
INCOMPLETE
mozilla1.4beta
People
(Reporter: mozeditor, Unassigned)
References
(Depends on 1 open bug)
Details
(Keywords: perf, Whiteboard: [perf]patch in 35295)
We didn't discuss this at the mail-reply perf meeting, but part of the editor
overhead for mailcite insertion is a collection of postprocessing steps that can
definitely go away for the plaintext mail case, and can almost certainly be
speeded up for the html compose case.
Reporter | ||
Updated•24 years ago
|
Target Milestone: mozilla0.9.1 → mozilla0.9.2
Comment 2•24 years ago
|
||
This bug is also not making the release??
Reporter | ||
Comment 3•24 years ago
|
||
It is part of a larger checkin that will land in 0.9.1.
For html messages, I can break it out seperately and land it immediatley if you
like. For plaintext messages, it depends on the other work that will be a week
or two.
Status: NEW → ASSIGNED
Reporter | ||
Comment 4•24 years ago
|
||
pulling back some bugs which may be fixed by the whitespace work.
Target Milestone: mozilla0.9.2 → mozilla0.9.1
Reporter | ||
Comment 5•24 years ago
|
||
There is a patch which does this checked into bug 39295.
Whiteboard: patch in 39295
Comment 7•24 years ago
|
||
PDT moving to 0.9.2 per triage session with beppe
Target Milestone: mozilla0.9.1 → mozilla0.9.2
Updated•24 years ago
|
Keywords: perf
Whiteboard: patch in 35295 → [perf]patch in 35295
Target Milestone: mozilla0.9.2 → mozilla1.0
Comment 8•23 years ago
|
||
Bugs targeted at mozilla1.0 without the mozilla1.0 keyword moved to mozilla1.0.1
(you can query for this string to delete spam or retrieve the list of bugs I've
moved)
Target Milestone: mozilla1.0 → mozilla1.0.1
Comment 9•23 years ago
|
||
removing myself from the cc list
Comment 10•22 years ago
|
||
does this depend on bug 35295 ? (since the patch is suppost to be in there?)
Reporter | ||
Comment 11•22 years ago
|
||
The days of having a half dozen milestones out in front of us to divide bugs
between seem to be gone, though I dont know why. Lumping everything together as
far out as I can. I'll pull back things that I am working on as I go.
Target Milestone: mozilla1.0.1 → mozilla1.2beta
Reporter | ||
Comment 12•22 years ago
|
||
[ushing these out as far as bugzilla will let me. I'll pull them back as I work
on them.
Target Milestone: mozilla1.2beta → mozilla1.4beta
Updated•18 years ago
|
QA Contact: sujay → editor
Updated•18 years ago
|
Assignee: mozeditor → nobody
Status: ASSIGNED → NEW
Comment 13•6 years ago
|
||
Moving to p3 because no activity for at least 1 year(s).
See https://github.com/mozilla/bug-handling/blob/master/policy/triage-bugzilla.md#how-do-you-triage for more information
Priority: P2 → P3
Comment 14•2 years ago
|
||
In the process of migrating remaining bugs to the new severity system, the severity for this bug cannot be automatically determined. Please retriage this bug using the new severity system.
Severity: major → --
Comment 15•2 years ago
|
||
There is no detail for the performance issue, and I'm rewriting editor to get rid of all centralized post-processing when I touch each handler. Therefore, this should be handled in a new bug if there is a performance issue even in these days.
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•