Closed Bug 172490 Opened 22 years ago Closed 22 years ago

Store Command Controller ids and add attributes to get controllers using these IDs

Categories

(Core :: DOM: Editor, defect)

All
Windows 2000
defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla1.2beta

People

(Reporter: cmanske, Assigned: cmanske)

References

Details

The current strategy of looking for controllers based on which interface they
implimement is not reliable. When each of the 2 default controllers are created in 
nsEditingSession::SetupFrameControllers(), the resulting IDs should 
be obtained by nsIControllers::GetControllerId() and stored as member vars.
I suggest adding something like these to nsIEditingSession.idl :
  readonly attribute nsIBaseEditorController baseEditorController;
  readonly attribute nsIBaseEditorController composerController;
and use nsIControllers::GetControllerById() to get the appropriate controller.
Blocks: edembed
Status: NEW → ASSIGNED
Keywords: nsbeta1
Hardware: PC → All
Target Milestone: --- → mozilla1.2beta
You can't use nsIBaseEditorController in nsIEditingSession. Any interface in a
frozen API has itself to be frozen. I'm not sure controllers should be
accessible via nsIEditingSession at all; it's polluting this api with unrelated
stuff.
Fixed as part of work on bug 174439
Status: ASSIGNED → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.