UnifiedComplete should set the default index before adding search @alias autofill matches
Categories
(Firefox :: Address Bar, defect, P1)
Tracking
()
Tracking | Status | |
---|---|---|
firefox66 | --- | fixed |
People
(Reporter: adw, Assigned: adw)
References
Details
Attachments
(1 file)
I found this while working on the patch in bug 1520665 (plus more WIP autofill work). When UnifiedComplete adds @alias autofill matches, first it adds the match, and then it calls this._result.setDefaultIndex(0). That means that the quantumbar UnifiedComplete provider doesn't recognize @alias autofill matches because when matches are added, it checks that the default index == 0, but because the default index is set after adding the match in this case, it remains -1.
Every other time UnifiedComplete adds autofill matches, it first sets the default index before adding the match, so this is just an error in UnifiedComplete's adding @alias autofill matches. However, this doesn't seem to actually impact the legacy urlbar and autocomplete controller at all.
Assignee | ||
Comment 1•7 years ago
|
||
Comment 3•7 years ago
|
||
bugherder |
Description
•