Closed
Bug 362163
Opened 18 years ago
Closed 18 years ago
Restore onerrorcommand autocomplete handlers
Categories
(SeaMonkey :: Autocomplete, defect)
SeaMonkey
Autocomplete
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: ajschult784, Assigned: ajschult784)
Details
Attachments
(1 file)
1.36 KB,
patch
|
neil
:
review-
|
Details | Diff | Splinter Review |
I removed onerrorcommand as part of bug 255731 at Neil's suggestion (bug 255731 comment 7), but I now think that was not the right thing to do. autocomplete still tries to fire it http://bonsai.mozilla.org/cvsblame.cgi?file=mozilla/xpfe/components/autocomplete/resources/content/autocomplete.xml&rev=1.136&mark=869,970#869 and some consumers still try to set an actual handler http://lxr.mozilla.org/seamonkey/search?string=onerrorcommand
Assignee | ||
Comment 1•18 years ago
|
||
Comment 2•18 years ago
|
||
Comment on attachment 246870 [details] [diff] [review] patch Hewitt removed support for onerrorcommand in revision 1.67 for some reason. If you really want to restore it you would also have to undo those changes.
Attachment #246870 -
Flags: review?(neil) → review-
Assignee | ||
Comment 3•18 years ago
|
||
He switched from using fireInit, fireTextCommand, fireErrorCommand and fireTextRevert methods to just a single _fireEvent method... but I don't see anything that actually removed support.
Comment 4•18 years ago
|
||
Yes, but that uses the attribute, not the field.
Status: ASSIGNED → RESOLVED
Closed: 18 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•