Closed Bug 12421 Opened 25 years ago Closed 25 years ago

string bundle needs to be moved to editor app shell

Categories

(Core :: DOM: Editor, defect, P1)

Product:
Core
Component:
DOM: Editor
Platform:
All
Windows NT
Type:
defect

Tracking

()

Status:
VERIFIED FIXED

People

(Reporter: buster, Assigned: cmanske)

References

(
URL
)

Details

from the newsgroup:

In article <37C2F725.9177F83E@netscape.com>, Steve Clark
<buster@netscape.com> wrote:

> 75% of our initialization time is creating the string bundle.  I assume
> the string bundle is only needed if the editor is going to be used in a
> mode where it provides it's own UI (dialogs and such), and it isn't
> needed otherwise (as with the simple HTML text control.)  I'd like to
> add a boolean param to nsIEditor::Init() to control this.  I can't just
> make it a flag, because the flags are defined in higher level editors.
> Maybe we should reserve a few bits of the flags for nsIEditor itself?
> Then I could just use the flags param.

Charlie and I have talked about the string bundle before, and
agreed that it should be moved into the editorShell anyway.
Recall that we're trying to keep all editor UI-related stuff
in the editor shell.

Charlie or I could do that work at any time.

Simon
Priority: P3 → P2
Priority: P2 → P1
Target Milestone: M10
simon: the priority on this has been escalated.  It's a fairly substantial part
of the performance problem with text controls, and text controls will be turned
on by default very, very soon.  Please get this done as soon as reasonably
possible.  Thanks.
Depends on: 12158
Assignee: sfraser → cmanske
charlie will handle this
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Checked in 8/28
Buster/Charley, can you mark this verified-fixed...thanks!
Status: RESOLVED → VERIFIED
verified.
You need to log in before you can comment on or make changes to this bug.