Closed
Bug 180657
Opened 22 years ago
Closed 20 years ago
XBL event handling incorrectly deregisters
Categories
(Core :: XBL, defect)
Tracking
()
RESOLVED
EXPIRED
People
(Reporter: conor, Assigned: hyatt)
References
()
Details
Attachments
(1 file)
|
2.53 KB,
application/x-zip-compressed
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2b) Gecko/20021016
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2b) Gecko/20021016
XBL event handling is deregistered after a particular sequence of DOM operations
that implement a "delete to previous line" option. The enclosed link has a full
example of the behavior and contrasts the XBL registration problem with
problem-free DOM event listener registration in the same circumstances.
Reproducible: Always
Steps to Reproduce:
See referenced link and attached files. Follow five steps in the file description.
Actual Results:
addListener event handler is fine but XBL registered event handlers are
deregistered.
Expected Results:
don't deregister XBL.
happens in Phoenix too (which isn't a big surprise I suppose :-))
| Reporter | ||
Comment 1•22 years ago
|
||
| Reporter | ||
Updated•22 years ago
|
Summary: XBL event handling is incorrectly deregisters → XBL event handling incorrectly deregisters
Updated•22 years ago
|
Flags: blocking1.3a?
Updated•22 years ago
|
Flags: blocking1.3a? → blocking1.3a-
Comment 2•20 years ago
|
||
This is an automated message, with ID "auto-resolve01".
This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.
While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.
If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.
The latest beta releases can be obtained from:
Firefox: http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey: http://www.mozilla.org/projects/seamonkey/
Comment 3•20 years ago
|
||
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•