Closed Bug 393231 Opened 17 years ago Closed 2 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)

Product:
Toolkit
Component:
Form Manager
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
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
Product: Firefox → Toolkit
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
Assignee: nobody → ffung
Depends on: asyncFormAC
Assignee: felix.the.cheshire.cat → nobody
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
No longer depends on: asyncFormAC
No longer depends on: 393191

We'd need a bit more description to make this actionable.

Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.