Closed
Bug 193548
Opened 22 years ago
Closed 19 years ago
Testcase for javascript object button handleEvent
Categories
(Core :: DOM: Events, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: angel5lif, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3b) Gecko/20030215 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3b) Gecko/20030215 At the following url: http://mozilla.org/quality/browser/standards/javascript/tcmatrix/index.html, you are given the option to perform the handleEvent() test. However when you click on the url which takes you here: http://mozilla.org/quality/ngdriver/suites/javascript/but011.html . You get a not found error. Reproducible: Always Steps to Reproduce: 1. Goto http://mozilla.org/quality/browser/standards/javascript/tcmatrix/index.html 2. Click on the but011.html hyperlink to http://mozilla.org/quality/ngdriver/suites/javascript/but011.html 3. Actual Results: You get a not found error Expected Results: It should have performed the test for handleEvent()
Comment 1•22 years ago
|
||
not browser
Assignee: asa → endico
Status: UNCONFIRMED → NEW
Component: Browser-General → webmaster@mozilla.org
Ever confirmed: true
Product: Browser → mozilla.org
QA Contact: asa → imajes
Version: Trunk → other
Comment 2•21 years ago
|
||
Sending to DOM HTML, this test needs to be written.
Assignee: endico → general
Component: webmaster@mozilla.org → DOM: HTML
Product: mozilla.org → Browser
QA Contact: imajes → ian
Version: other → Trunk
Comment 3•21 years ago
|
||
Now that I think about it... why should HTMLButtonElement have a handleEvent method? Should this test even exist?
Comment 4•21 years ago
|
||
The only handleEvent() method that exists in the DOM is on the EventListener method, and no elements are expected to implement that interface, so this seems like a bogus test to me.
Comment 5•20 years ago
|
||
"Any object that can register event handlers is an event receiver. This method [handleEvent] explicitly calls the event handler of the event receiver and bypasses the capturing hierarchy." http://devedge.netscape.com/library/manuals/2000/javascript/1.3/guide/evnt.html#1010446 It seems to me that this is what dispatchEvent method does in DOM 2 Events. "This method [dispatchEvent] allows the dispatch of events into the implementations event model. Events dispatched in this manner will have the same capturing and bubbling behavior as events dispatched directly by the implementation. The target of the event is the EventTarget on which dispatchEvent is called." http://www.w3.org/TR/2000/REC-DOM-Level-2-Events-20001113/events.html#Events-EventTarget-dispatchEvent
Comment 6•19 years ago
|
||
As far as I can see, NS 4.x handleEvent has been removed from all possible objects (or likely was never implemented in Mozilla-based browsers) and DOM 2 Events dispatchEvent method is the appropriate replacement to use. handleEvent method is not working in 5 years old NS 6.1 (rv: 0.9.2) but dispatchEvent is; I can't find a single Mozilla-based browser which support handleEvent according to NS 4.x specs. Component -> DOM: Events Resolving as INVALID
Status: NEW → RESOLVED
Closed: 19 years ago
Component: DOM: HTML → DOM: Events
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•