Ext.data.JsonP.Ext_EventManager({"alternateClassNames":[],"aliases":{},"enum":null,"parentMixins":[],"tagname":"class","subclasses":[],"extends":null,"uses":[],"html":"
Files
Registers event handlers that want to receive a normalized EventObject instead of the standard browser event and provides\nseveral useful events directly.
\n\nSee Ext.EventObject for more details on normalized event objects.
\nAdditionally, allow the 'DOM' listener thread to complete (usually desirable with mobWebkit, Gecko)\nbefore firing the entire onReady chain (high stack load on Loader) by specifying a delay value.\nDefaults to 1ms.
\nDefaults to: 1
Check if we have bound our global onReady listener
\nDefaults to: false
Check if fireDocReady has been called
\nDefaults to: false
Fires when an event handler finishes its run, just before returning to browser control.
\n\nThis includes DOM event handlers, Ajax (including JSONP) event handlers, and TaskRunners
\n\nThis can be useful for performing cleanup, or update tasks which need to happen only\nafter all code in an event handler has been run, but which should not be executed in a timer\ndue to the intervening browser reflow/repaint which would take place.
\nOptions to parse for the 4th argument to addListener.
\nDefaults to: /^(?:scope|delay|buffer|single|stopEvent|preventDefault|stopPropagation|normalized|args|delegate|freezeEvent)$/
Holds references to any onReady functions
\nHolds references to any onReady functions
\nContains a list of all document mouse downs, so we can ensure they fire even when stopEvent is called.
\nContains a list of all document mouse downs, so we can ensure they fire even when stopEvent is called.
\nnote 1: IE fires ONLY the keydown event on specialkey autorepeat\nnote 2: Safari < 3.1, Gecko (Mac/Linux) & Opera fire only the keypress event on specialkey autorepeat\n(research done by Jan Wolter at http://unixpapa.com/js/key.html)
\nAppends an event handler to an element. The shorthand version on is equivalent.\nTypically you will use Ext.Element.addListener directly on an Element in favor of\ncalling this version.
\n\non is an alias for addListener.
\nThe html element or id to assign the event handler to.
\n\nThe name of the event to listen for.
\n\nThe handler function the event invokes. A String parameter\nis assumed to be method name in scope
object, or Element object if no scope is provided.
The EventObject describing the event.
\n\nThe Element which was the target of the event.\nNote that this may be filtered by using the delegate
option.
The options object from the addListener call.
\n\nThe scope (this
reference) in which the handler function is executed.\nDefaults to the Element.
An object containing handler configuration properties.\nThis may contain any of the following properties (See Ext.Element.addListener\nfor examples of how to use these options.):
\n\nThe scope (this
reference) in which the handler function is executed. Defaults to the Element.
A simple selector to filter the target or look for a descendant of the target
\n\nTrue to stop the event. That is stop propagation, and prevent the default action.
\n\nTrue to prevent the default action
\n\nTrue to prevent event propagation
\n\nFalse to pass a browser event to the handler function instead of an Ext.EventObject
\n\nThe number of milliseconds to delay the invocation of the handler after te event fires.
\n\nTrue to add a handler to handle just the next firing of the event, and then remove itself.
\n\nCauses the handler to be scheduled to run in an Ext.util.DelayedTask delayed\nby the specified number of milliseconds. If the event fires again within that time, the original\nhandler is not invoked, but the new handler is scheduled in its place.
\n\nOnly call the handler if the event was fired on the target Element,\nnot if the event was bubbled up from a child node.
\n\nBinds the appropriate browser event for checking if the DOM has loaded.
\nChecks whether the event's relatedTarget is contained inside (or is) the element.
\nWe know the document is loaded, so trigger any onReady events.
\nFires the unload event for items bound with onWindowUnload
\nGets the event cache object for a particular element
\nThe element
\nThe event cache object
\nGet the id of the element. If one has not been assigned, automatically assign it.
\nThe element to get the id for.
\nid
\nGets the related target from the event.
\nThe event
\nThe related target.
\ndetects whether the EventManager has been placed in a paused state for synchronization\nwith external debugging / perf tools (PageAnalyzer)
\nAppends an event handler to an element. The shorthand version on is equivalent.\nTypically you will use Ext.Element.addListener directly on an Element in favor of\ncalling this version.
\n\non is an alias for addListener.
\nThe html element or id to assign the event handler to.
\n\nThe name of the event to listen for.
\n\nThe handler function the event invokes. A String parameter\nis assumed to be method name in scope
object, or Element object if no scope is provided.
The EventObject describing the event.
\n\nThe Element which was the target of the event.\nNote that this may be filtered by using the delegate
option.
The options object from the addListener call.
\n\nThe scope (this
reference) in which the handler function is executed.\nDefaults to the Element.
An object containing handler configuration properties.\nThis may contain any of the following properties (See Ext.Element.addListener\nfor examples of how to use these options.):
\n\nThe scope (this
reference) in which the handler function is executed. Defaults to the Element.
A simple selector to filter the target or look for a descendant of the target
\n\nTrue to stop the event. That is stop propagation, and prevent the default action.
\n\nTrue to prevent the default action
\n\nTrue to prevent event propagation
\n\nFalse to pass a browser event to the handler function instead of an Ext.EventObject
\n\nThe number of milliseconds to delay the invocation of the handler after te event fires.
\n\nTrue to add a handler to handle just the next firing of the event, and then remove itself.
\n\nCauses the handler to be scheduled to run in an Ext.util.DelayedTask delayed\nby the specified number of milliseconds. If the event fires again within that time, the original\nhandler is not invoked, but the new handler is scheduled in its place.
\n\nOnly call the handler if the event was fired on the target Element,\nnot if the event was bubbled up from a child node.
\n\nAdds a listener to be notified when the document is ready (before onload and before images are loaded).
\n\nExt.onDocumentReady is an alias for onDocumentReady.
\nThe method the event invokes.
\nThe scope (this
reference) in which the handler function executes.\nDefaults to the browser window.
Options object as passed to Ext.Element.addListener.
\nAdds a listener to be notified when the browser window is resized and provides resize event buffering (100 milliseconds),\npasses new viewport width and height to handlers.
\nThe handler function the window resize event invokes.
\nThe scope (this
reference) in which the handler function executes. Defaults to the browser window.
Options object as passed to Ext.Element.addListener
\nAdds a listener to be notified when the browser window is unloaded.
\nThe handler function the window unload event invokes.
\nThe scope (this
reference) in which the handler function executes. Defaults to the browser window.
Options object as passed to Ext.Element.addListener
\nThis strategy has minimal benefits for Sencha solutions that build themselves (ie. minimal initial page markup).\nHowever, progressively-enhanced pages (with image content and/or embedded frames) will benefit the most from it.\nBrowser timer resolution is too poor to ensure a doScroll check more than once on a page loaded with minimal\nassets (the readystatechange event 'complete' usually beats the doScroll timer on a 'lightly-loaded' initial document).
\nPrevents the browsers default handling of the event.
\nThe event to prevent the default
\nRecursively removes all previous added listeners from an element and its children. Typically you will use Ext.Element.purgeAllListeners\ndirectly on an Element in favor of calling this version.
\nThe id or html element from which to remove all event handlers.
\nThe name of the event.
\nRemoves all event handers from an element. Typically you will use Ext.Element.removeAllListeners\ndirectly on an Element in favor of calling this version.
\nThe id or html element from which to remove all event handlers.
\nRemoves an event handler from an element. The shorthand version un is equivalent. Typically\nyou will use Ext.Element.removeListener directly on an Element in favor of calling this version.
\n\non is an alias for addListener.
\nThe id or html element from which to remove the listener.
\n\nThe name of the event.
\n\nThe handler function to remove. This must be a reference to the function passed\ninto the addListener call.
\n\nIf a scope (this
reference) was specified when the listener was added,\nthen this must refer to the same object.
Resolve any text nodes accounting for browser differences.
\nThe node
\nThe resolved node
\nStop the event (preventDefault and stopPropagation)
\nThe event to stop
\nCancels bubbling of the event.
\nThe event to stop bubbling.
\nRemoves an event handler from an element. The shorthand version un is equivalent. Typically\nyou will use Ext.Element.removeListener directly on an Element in favor of calling this version.
\n\non is an alias for addListener.
\nThe id or html element from which to remove the listener.
\n\nThe name of the event.
\n\nThe handler function to remove. This must be a reference to the function passed\ninto the addListener call.
\n\nIf a scope (this
reference) was specified when the listener was added,\nthen this must refer to the same object.