There is no composition events in the "Event Listener Breakpoints"
Categories
(DevTools :: Debugger, defect, P3)
Tracking
(firefox105 verified)
Tracking | Status | |
---|---|---|
firefox105 | --- | verified |
People
(Reporter: masayuki, Assigned: luke.swiderski, Mentored)
References
(Blocks 1 open bug)
Details
(Keywords: good-first-bug, inputmethod)
Attachments
(2 files)
- Open DevTools and go to Debugger tab, and see "Event Listener Breakpoints"
What happened?
There is no composition events such as compositionstart
, compositionupdate
nor compositionend
.
What should have happened?
They should be listed (perhaps, in Keyboard
?)
Reporter | ||
Updated•3 years ago
|
Comment 1•3 years ago
|
||
Thanks for reporting!
We should add this and this would likely go under Keyboard
events.
For whoever picks this up
Should not be too difficult to do. See Bug 1674307 as an example
Comment 2•3 years ago
|
||
Hi, first-time contributor here. I think I'd like to pick this up.
I noticed that in Bug 1674307 the fix included some integration tests, however I don't see tests for all the options in this menu. Should I add tests for this one?
Comment 3•3 years ago
|
||
Updated•3 years ago
|
Comment 4•3 years ago
|
||
(In reply to Patrick Gregory from comment #2)
Hi, first-time contributor here. I think I'd like to pick this up.
Thanks for picking this up, Patrick.
I noticed that in Bug 1674307 the fix included some integration tests, however I don't see tests for all the options in this menu. Should I add tests for this one?
Yeah, we should add tests for this.
We should eventually add test for all the other options.
Comment 5•3 years ago
|
||
Apologies. I think this might be out of my depth at the moment.
Comment 6•3 years ago
|
||
This good-first-bug hasn't had any activity for 2 months, it is automatically unassigned.
For more information, please visit auto_nag documentation.
Assignee | ||
Comment 7•3 years ago
|
||
Add compositionstart, compositionupdate and compositionend
to keyboard event-listener-breakpoints.
Add mochitests for each.
Updated•3 years ago
|
Comment 9•2 years ago
|
||
bugherder |
Updated•2 years ago
|
I managed to reproduce this issue on Firefox 104.0(build ID: 20220818191623) on Ubuntu 22.04, using the STR from the Description. Verified as fixed on Firefox 105.0b5(build ID: 20220830185924) and Nightly 106.0a1(build ID: 20220831215447) on Ubuntu 22.04, Windows 10, macOS 12.
Description
•