Closed
Bug 1434837
Opened 6 years ago
Closed 6 years ago
autocomplete should listen to keypress events at the system event group
Categories
(Toolkit :: Autocomplete, enhancement, P1)
Toolkit
Autocomplete
Tracking
()
RESOLVED
FIXED
mozilla60
Tracking | Status | |
---|---|---|
firefox60 | --- | fixed |
People
(Reporter: masayuki, Assigned: masayuki)
References
(Depends on 1 open bug)
Details
Attachments
(1 file)
We'll stop dispatching keypress events for non-printable keys and non-printable key combinations. Therefore, autocomplete should stop using keypress events to handle such keys and key combinations.
Assignee | ||
Comment 1•6 years ago
|
||
https://treeherder.mozilla.org/#/jobs?repo=try&revision=6b6167dd241c6aea32cc406eeadc828df43921fb
Updated•6 years ago
|
Priority: -- → P1
Assignee | ||
Comment 2•6 years ago
|
||
https://treeherder.mozilla.org/#/jobs?repo=try&revision=dce39f790528dd7f9b6fea5815095fb7a0072ee2
Assignee | ||
Comment 3•6 years ago
|
||
https://treeherder.mozilla.org/#/jobs?repo=try&revision=53ae7e9ef1a59b6ef77c79b4df787c94c2e7726f
Assignee | ||
Comment 4•6 years ago
|
||
Hmm, if we change some part of keypress event listeners to keydown event listeners, the order of key event listeners are changed between other modules. That causes a lot of oranges which are difficult to understand. Without event listener order debugging system, we cannot use such ideal approach... So, perhaps, we should just use keypress event listeners at the system event group for now, unfortunately.
OS: Unspecified → All
Hardware: Unspecified → All
Summary: autocomplete should handle keydown event if it needs to handle non-printable key or key combination → autocomplete should listen to keypress events at the system event group
Version: unspecified → Trunk
Assignee | ||
Comment 5•6 years ago
|
||
https://treeherder.mozilla.org/#/jobs?repo=try&revision=3ed5963b10fbe59f469f5df727bf04c445a9a8be
Assignee | ||
Comment 6•6 years ago
|
||
https://treeherder.mozilla.org/#/jobs?repo=try&revision=9e2329d62d016ae3e58f770a8b942fb5a440a539
Assignee | ||
Comment 7•6 years ago
|
||
https://treeherder.mozilla.org/#/jobs?repo=try&revision=6e9426401997c34cffcf342956628e59fd743854
Assignee | ||
Comment 8•6 years ago
|
||
https://treeherder.mozilla.org/#/jobs?repo=try&revision=fc46656ca2a606c58694e38773f31d1d0b3b4d9d
Assignee | ||
Comment 9•6 years ago
|
||
https://treeherder.mozilla.org/#/jobs?repo=try&revision=38cbc1c7083b8bdcb1903b8e29d0ae4e3dd3bb6e
Comment hidden (mozreview-request) |
Comment 11•6 years ago
|
||
mozreview-review |
Comment on attachment 8950533 [details] Bug 1434837 - Make autocomplete and satchel listen to keypress event at the system event group https://reviewboard.mozilla.org/r/219806/#review227218 LGTM, thanks! ::: toolkit/content/tests/chrome/test_autocomplete_mac_caret.xul:63 (Diff revision 1) > + }, {once: true}); > + synthesizeKey(key, {}); > + if (result) { > + ok(keypressFired, testid + " keypress event should be fired"); > + } else { > + ok(!keypressFired, testid + " keypress event shouldn't be fired"); nit: you could probably unify these: is(keypressFired, result, `${testid} keypress event should${result ? "" : " not"} be fired`);
Attachment #8950533 -
Flags: review?(mak77) → review+
Assignee | ||
Comment 12•6 years ago
|
||
https://treeherder.mozilla.org/#/jobs?repo=try&revision=2180450ca3cefb25f81a99f5043ebd1537e22249
Comment hidden (mozreview-request) |
Comment 14•6 years ago
|
||
Pushed by masayuki@d-toybox.com: https://hg.mozilla.org/integration/autoland/rev/c0b4ca69376c Make autocomplete and satchel listen to keypress event at the system event group r=mak
Comment 15•6 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/c0b4ca69376c
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
status-firefox60:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla60
You need to log in
before you can comment on or make changes to this bug.
Description
•