Closed
Bug 393231
Opened 18 years ago
Closed 3 years ago
if browser.formfill.enable is false, nsFormAutoComplete.js's autoCompleteSearch should return a non-null "empty" result with nsIAutoCompleteResult::RESULT_NOMATCH
Categories
(Toolkit :: Form Manager, defect)
Toolkit
Form Manager
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: moco, Unassigned)
Details
spun out from bug #393191
per gavin:
if browser.formfill.enable is false, nsFormHistory::AutoCompleteSearch should really return a non-null "empty" result with nsIAutoCompleteResult::RESULT_NOMATCH
|
Assignee | |
Updated•17 years ago
|
Product: Firefox → Toolkit
|
||
Updated•13 years ago
|
Summary: if browser.formfill.enable is false, nsFormHistory::AutoCompleteSearch should really return a non-null "empty" result with nsIAutoCompleteResult::RESULT_NOMATCH → if browser.formfill.enable is false, nsFormAutoComplete::AutoCompleteSearch should really return a non-null "empty" result with nsIAutoCompleteResult::RESULT_NOMATCH
|
|
||
Updated•13 years ago
|
Assignee: nobody → ffung
|
|
||
Updated•13 years ago
|
Depends on: asyncFormAC
|
||
Updated•12 years ago
|
Assignee: felix.the.cheshire.cat → nobody
|
|
||
Updated•12 years ago
|
Summary: if browser.formfill.enable is false, nsFormAutoComplete::AutoCompleteSearch should really return a non-null "empty" result with nsIAutoCompleteResult::RESULT_NOMATCH → if browser.formfill.enable is false, nsFormAutoComplete.js's autoCompleteSearch should return a non-null "empty" result with nsIAutoCompleteResult::RESULT_NOMATCH
|
|
||
Updated•12 years ago
|
No longer depends on: asyncFormAC
|
||
Comment 1•3 years ago
|
||
We'd need a bit more description to make this actionable.
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•