Closed
Bug 1679424
Opened 4 years ago
Closed 3 years ago
Merge multiple select event dispatching mechanisms
Categories
(Core :: DOM: Selection, task)
Core
DOM: Selection
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: saschanaz, Unassigned)
References
(Blocks 1 open bug)
Details
Currently there are three mutually exclusive way to fire select events:
HTMLInputElement::Select
andHTMLTextAreaElement::Select
directly dispatches select eventselectionStart
/selectionEnd
setters callTextControlState::SetSelectionRange
which dispatches the eventTextInputListener::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.
Updated•4 years ago
|
Severity: -- → N/A
Reporter | ||
Comment 1•3 years ago
|
||
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.
Description
•