140303 - Selection fires off too many bogus NotifySelectionChanged() notifications.

Status: NEW

(Core :: DOM: Selection, defect, P5)

Description

[kinmoz]

If you fire up composer and put a break point in 
nsTypedSelection::NotifySelectionListeners(), you'll notice that clicking the 
mouse anywhere in the composer window will generate 2 NotifySelectionChanged() 
notification calls even though the selection hasn't really changed.

IMO, selection should only be firing these notifications when the start or end 
points of a range in the selection have changed, or ranges have been 
added/removed from the selection.

This is contributing to bugs like bug 125345, because the editor TypeInState() 
assumes that it will only be notified for true selection changes.

Comment 1

[Aaron Leventhal]

Without a fix for this bug, we had to implement a workaround in accessibility
code - see bug 168106.

Comment 2

[Vedran Miletic]

retargeting

Comment 3

[Jens Stutte [:jstutte]]

Bulk-downgrade of unassigned, >=5 years untouched DOM/Storage bugs' priority.

If you have reason to believe this is wrong (especially for the severity), please write a comment and ni :jstutte.