Closed
Bug 636134
Opened 14 years ago
Closed 12 years ago
HTMLBodyElement onundo/onredo events not firing
Categories
(Core :: DOM: Events, defect)
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: marc.fawzi, Unassigned)
Details
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:2.0b10) Gecko/20100101 Firefox/4.0b10
Build Identifier: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:2.0b10) Gecko/20100101 Firefox/4.0b10
the body.onundo and body.onredo events don't seem to be implemented contrary to what is suggested in the MDC doc: https://developer.mozilla.org/en/DOM/HTMLBodyElement
Reproducible: Always
Steps to Reproduce:
1. document.body.addEventListener("undo", hanlder, false)
2. handler() {alert('undo was triggered');
3. go to menu and click Undo or do ctrl/cmd-z
Actual Results:
the undo event is not fired
Expected Results:
the undo/redo events of the body element are supposed to fire when user triggers undo/redo action via mani menu, context menu or keyboard shortcuts
Related:
How do i volunteer to help w firefox development?
Comment 1•14 years ago
|
||
Could you attach a reduced testcase to this bug please.
Can you also confirm the problem exists with the latest nightly and a clean profile:
http://support.mozilla.com/en-US/kb/Basic%20Troubleshooting#w_make-a-new-profile
http://nightly.mozilla.org/
(In reply to comment #0)
> How do i volunteer to help w firefox development?
http://www.mozilla.org/contribute/
Component: General → DOM: Events
Product: Firefox → Core
QA Contact: general → events
Version: unspecified → Trunk
![]() |
||
Comment 2•14 years ago
|
||
The devmo page is just wrong. We don't implement this event, and never have.
ccing page author in case I'm missing something here...
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 3•14 years ago
|
||
Updated the devmo page to show these events as unimplemented.
Comment 4•12 years ago
|
||
Given that:
1) We don't implement these
2) WebKit doesn't implement these (bug 26139), and as far as I can find neither Opera, nor IE.
3) These events have been removed from HTML5, both HTML 5 W3C (CR) and HTML5 WHATWG. (See: http://html5.org/tools/web-apps-tracker?from=6529&to=6530 )
I think it is safe to RESOLVED this bug as WONTFIX. (Reopen if I'm wrong)
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•