Closed
Bug 1300919
Opened 8 years ago
Closed 8 years ago
[e10s regression] Double-clicking a focused <input> doesn't open the autocomplete popup
Categories
(Toolkit :: Form Manager, defect, P1)
Tracking
()
RESOLVED
DUPLICATE
of bug 1183037
People
(Reporter: MattN, Unassigned)
References
Details
(Keywords: regression)
STR:
1) Focus a field which would have form history (or datalist) results such that the autocomplete popup doesn't appear
2) Double-click in that same field
Expected results:
The autocomplete popup should open (though I do see a Flicker in between the clicks on non-e10s). This behaviour matches Chrome.
Actual result:
The autocomplete popup opens on the first click and then closes on the second one. Even worse is that it leaves the field in a bad state in that the down arrow on the keyboard also doesn't work after step 2 (regardless of how many times it's pressed) so it makes it seem like there is no form history or suggestions for the field. This also affects password manager autocompletion.
Note that double-clicking an unfocused field shows the autocomplete dropdown as expected. The bug is with a focused field.
Last good revision: f986e55c4e0b (2015-05-29)
First bad revision: 45a4d6336c73 (2015-05-30)
Pushlog:
https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=f986e55c4e0b&tochange=45a4d6336c73
The problem is likely in one of the three bugs: bug 1162330, bug 1162329, bug 1024437
Before those bugs the autocomplete popup didn't work at all in e10s it seems so it may not be worth looking to much at them.
Reporter | ||
Updated•8 years ago
|
status-firefox51:
--- → affected
Reporter | ||
Comment 1•8 years ago
|
||
[Tracking Requested - why for this release]: non-e10s regression due to switching non-e10s to the already broken e10s code path
Note that the problem occurs only when E10S is enabled before the code paths were unified in bug 1294502. With the unified code paths this is also broken with non-e10s.
Non-E10S Regression Range:
Last good revision: 97a52326b06a07930216ebefa5af333271578904 (2016-08-18)
First bad revision: 23c2ec5544b9e0a74a047b87b594e4c36a8fe95c (2016-08-19)
Pushlog:
https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=97a52326b06a07930216ebefa5af333271578904&tochange=23c2ec5544b9e0a74a047b87b594e4c36a8fe95c
Comment 2•8 years ago
|
||
This is probably a dupe of bug 1183037.
![]() |
||
Updated•8 years ago
|
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
Updated•8 years ago
|
tracking-firefox51:
? → ---
Updated•8 years ago
|
status-firefox48:
affected → ---
status-firefox49:
affected → ---
status-firefox50:
affected → ---
status-firefox51:
affected → ---
tracking-e10s:
? → ---
You need to log in
before you can comment on or make changes to this bug.
Description
•