Closed Bug 1838752 Opened 2 years ago Closed 2 years ago

DropMutationEvent should handle EVENT_INNER_REORDER

Categories

(Core :: Disability Access APIs, defect)

defect

Tracking

()

RESOLVED FIXED
116 Branch
Tracking Status
firefox116 --- fixed

People

(Reporter: nlapre, Assigned: nlapre)

References

(Blocks 1 open bug)

Details

Attachments

(1 file)

We should assert in DropMutationEvent that the given event is not an inner reorder, since that indicates it's already been dropped (which shouldn't happen). At the moment, the error would be confusing, since we'd hit this else block assert as if we were expecting a hide event.

This isn't a big deal, but might be confusing. I noticed it while messing around with event coalescence.

This revision updates DropMutationEvent such that it handles other event
types besides REORDER, HIDE, and SHOW. If we somehow put a different event
type through this function (particularly an inner reorder, which indicates
a reorder event that's already been dropped), we should (and now do) handle
it more gracefully.

Assignee: nobody → nlapre
Status: NEW → ASSIGNED
Pushed by nlapre@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/3f7d6ae9fcce Handle other event types in DropMutationEvent,r=eeejay
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 116 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: