Talk:DOM event

message: While the inline model is not as flexible as other models, it is the only model that allow the registration of event handlers with custom arguments, e.g. name in the helloWorld method.
Not quite. Instead the browser creates an anonymous function that handles the event and that function calls the function with the argument specified. Eric B. and Rakim 22:12, 29 Apr 2005 (UTC)

message: According to google (and a bunch of others search engines) the ondomfocusout attribute is metioned in any other place but here. What's the source for this information?
:I have no idea when you wrote this (and I'm too lazy to check), but try this DOMFocusOut --Execvator 23:56, 7 May 2007 (UTC)
thread_title:  onDomFocusOut 

message: Say what DOM stands for!
What is * in "DOM*"?
:DOM stands for Document Object Model. What is in it is the elements, methods, and properties of the document. (Bjorn Tipling 18:04, 30 March 2006 (UTC)
replies: text: "DOM*" refers to every event whose name begins with "DOM". The star is being used as a wildcard character. (I've made this clearer in the article.) --81.178.31.210 15:02, 21 April 2006 (UTC)
thread_title:  DOM=? 

message: The description for the load an unload event was 'wrong'. They apply to both the document and elements. As it was, it sounded like they only applied to the document. I made some changes to reflect this, though it would be good if someone could rewrite it in a better way.
And yes, it is 'and' for load and 'or' for unload. --Execvator 23:56, 7 May 2007 (UTC)
thread_title:  (un)load event description 

message: Shouldn't there be a browser comparison of DOM events somewhere - like there are with HTML5 support, etc. It could be helpful since some browser support some events and some do not. Case in point Firefox recently added support for the readystatechange event - on this page it is listed as a "Microsoft-specific event" even though it is no longer exclusive to Micrsoft.
Does anyone else agree or disagree with this?
Ryan Jones (talk) 16:12, 26 June 2010 (UTC)
thread_title:  Browser Comparison for DOM Events? 

message: I observed in a Firefox extension that gBrowser.AddEventListener("load", ...) fires more often than expected:
When moving from one page to another, it appears that the listener is first called with the page being left and then (or maybe intertwined) with the new page. 
IMHO that does not match the description here.--Hagman-de (talk) 09:44, 13 August 2010 (UTC)
thread_title:  load fires more often? 

message: "DOM (Document Object Model) events allow event-driven programming languages like [...]"
This is wrong. The DOM Events are language agnostic. The mechanism is part of the DOM and not the language.
I.e. a DOM implementation's nodes implement the EventTarget interface. 
"Events are first captured until it reaches the target element, and then bubbled up"
This is wrong. This implies that the event target's capturing phase listeners would be called before the bubbling phase listeners, which is not the case. There is a third phase: AT_TARGET.
"To prevent an event from bubbling, developers must call the 'stopPropagation()' method of the event object." 
This is wrong. In fact it does what its name suggests: it stops propagation of an event. In any phase.
"To add parameters: [...]"
This is wrong. The function already closes over "name". What you suggest is needed only when "name"'s current value need to be preserved, which is irrelevant to the example, not specific to the event model, and thus misleading.
"Inner functions preserve their scope."
This is wrong. Functions close over the scope they are defined in. Also the 'outer' function. See above paragraph.
"Touch events"
Why are the TouchEvent, TouchList and TouchPoint interface definitions given, and not e.g. more fundamental interfaceslike Event, UIEvent, MouseEvent? And are such interface definitions relevant? And if so, do we need the interface definition and a description of it, or could this be more concise? Why not just point to the spec(s)?
Much of the rest is outdated or incomplete.
e.g. DOM L3 Event interface provides stopImmediatePropagation() method,
and HTML5 dnd spec is not mentioned at all.
Maybe I should write an article about horses, because I have read a blog about them, and I have even touched one! It'll start with "Horses are brown and they need horseshoes to walk".
212.186.3.85 (talk) 11:53, 19 June 2011 (UTC)
thread_title:  Wrong, misleading, irrelevant, outdated and incomplete 

message: The tables in this article distinguish between "type" and "attribute" (e.g. keypress versus onkeypress). What is meant with these two columns, and what are their differences? --Abdull (talk) 15:02, 28 April 2012 (UTC)
thread_title:  Type versus Attribute distinction? 

message: Hello fellow Wikipedians,
I have just added archive links to  on DOM events. Please take a moment to review my edit. If necessary, add  after the link to keep me from modifying it. Alternatively, you can add  to keep me off the page altogether. I made the following changes:
*Added archive https://web.archive.org/20100611124414/http://perfectionlabstips.wordpress.com:80/2008/12/01/which-browsers-support-native-domcontentloaded-event/ to http://perfectionlabstips.wordpress.com/2008/12/01/which-browsers-support-native-domcontentloaded-event/
When you have finished reviewing my changes, please set the checked parameter below to true to let others know.
Cheers.—cyberbot IITalk to my owner:Online 09:28, 10 January 2016 (UTC)
thread_title:  External links modified