Closed Bug 1679424 Opened 4 years ago Closed 3 years ago

Merge multiple select event dispatching mechanisms

Categories

(Core :: DOM: Selection, task)

Product:
Core
Component:
DOM: Selection
Type:
task

Tracking

()

Status:
RESOLVED WONTFIX

People

(Reporter: saschanaz, Unassigned)

References

(Blocks 1 open bug)

Details

Currently there are three mutually exclusive way to fire select events:

  1. HTMLInputElement::Select and HTMLTextAreaElement::Select directly dispatches select event
  2. selectionStart/selectionEnd setters call TextControlState::SetSelectionRange which dispatches the event
  3. TextInputListener::OnSelectionChange listens selection changes from mouse/keyboard actions and dispatches the event

This situation is needlessly complex. The third mechanism should be able to cover all the cases as the text control methods/setters eventually call it.

Bug 1679461 merged 1 and 2. I think 3 has a different intention and thus can't be merged right now. Closing.

Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.