1089553 - Suppress/Unsuppress the SelectionChangeEvents in form.js

Status: RESOLVED WONTFIX

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

Description

[Peter Chang[:pchang]]

This bug is the follw up bug from bug 1065955 comment 18.

(In reply to :Ehsan Akhgari (not reading bugmail, needinfo? me!) from comment #18)
> (In reply to peter chang[:pchang][:peter] from comment #17)
> > With Bug 1066515, it adds the fast path to resolve original problem but it
> > is easy to fall back to original path to hit the low performance problem[1].
> 
> So, I don't think that was the right approach either.  As I said, given that
> we *know* that this is a performance problem in that code, we should just
> suppress sending the selection events in that code in general.  We can
> surround that loop with a
> suppressSendingSelectionChangeEvents/unsuppressSendingSelectionChangeEvents
> calls (hopefully you can think of better function names ;) and in
> UpdateState, check a boolean condition based on that.

Comment 1

[(no longer active)]

Note that if we end up tailoring the selectionchange event only for the copy/paste bubble use case, this problem may go away and we may not need to do anything here.

Comment 2

[(no longer active)]

Do we still need to do this?

Comment 3

[Peter Chang[:pchang]]

(In reply to [Away: 1/29-2/20] from comment #2)
> Do we still need to do this?

Consider this in v3 period.

Comment 4

[Ting-Yu Lin [:TYLin] (UTC-8)]

The new AccessibleCaret does not fire SelectionChangeEvents. (bug 1172382)