Open Bug 583055 Opened 14 years ago Updated 2 years ago

Do not make use of the selection controller before the editor is initialized

Categories

(Core :: Disability Access APIs, defect)

defect

Tracking

()

People

(Reporter: davidb, Unassigned)

References

(Blocks 1 open bug)

Details

Probably the right fix is to make nsCaretAccessible::NotifySelectionChanged a runnable.

Ehsan tells me this is likely a regression from the lazy editor init work.

(See also Bug 577518)
Ehsan, what specifically is dangerous about our NotifySelectionChanged method? Are you worried about us using frames?
The selection controller is created as part of the editor initialization.  It simply does not exist before the editor has finished initializing.
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.