Closed Bug 286014 Opened 20 years ago Closed 1 year ago

Toolkit autocomplete code fires DOM* events it made up

Categories

(Toolkit :: Autocomplete, defect, P3)

x86
Linux
defect

Tracking

()

RESOLVED FIXED
124 Branch
Tracking Status
firefox124 --- fixed

People

(Reporter: bzbarsky, Assigned: serg)

References

Details

(Whiteboard: [fxcm-debt])

Attachments

(1 file)

The satchel and passwordmgr code seems to use a DOMAutoComplete event for its internal communication. Now using an event is fine, but naming it DOM* is probably rather suspect unless it's actually an event that's dispatched by the DOM (and an event that won't conflict with future DOM specs, even then, I would think). Perhaps this code should namespace the event appropriately? Does the DOM provide a reasonable way to namespace event names?
QA Contact: nobody → autocomplete
Per policy at https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Inactive_Bugs. If this bug is not an enhancement request or a bug not present in a supported release of Firefox, then it may be reopened.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INACTIVE
Still an issue liable to bite us if the DOM spec introduces such an event.
Status: RESOLVED → REOPENED
Resolution: INACTIVE → ---
Status: REOPENED → NEW
Priority: -- → P3
Severity: normal → S3
Assignee: nobody → sgalich
Status: NEW → ASSIGNED
Whiteboard: [fxcm-debt]
Pushed by sgalich@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/011da5ad84c7 removing unused DOMAutoComplete event r=credential-management-reviewers,issammani
Status: ASSIGNED → RESOLVED
Closed: 7 years ago1 year ago
Resolution: --- → FIXED
Target Milestone: --- → 124 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: