-
- Ext.fly(bd, '_internal').addClass(cls);
- return true;
- };
-
- /*
- * Assert Ext.isReady here. If Ext is loaded after the document is ready, none of the native
- * DOM onReady events will fire, because they have already passed.
- */
- Ext.isReady = initExtCss();
-
- if (!Ext.isReady) {
- Ext.onReady(initExtCss);
- }
-})();
-
-<div id="prop-Ext.EventManager-function"></div>/**
- * Code used to detect certain browser feature/quirks/bugs at startup.
- */
-(function(){
- var supports = Ext.apply(Ext.supports, {
- <div id="prop-Ext.EventManager-correctRightMargin"></div>/**
- * In Webkit, there is an issue with getting the margin right property, see
- * https://bugs.webkit.org/show_bug.cgi?id=13343
- */
- correctRightMargin: true,
-
- <div id="prop-Ext.EventManager-correctTransparentColor"></div>/**
- * Webkit browsers return rgba(0, 0, 0) when a transparent color is used
- */
- correctTransparentColor: true,
-
- <div id="prop-Ext.EventManager-cssFloat"></div>/**
- * IE uses styleFloat, not cssFloat for the float property.
- */
- cssFloat: true
- });
-
- var supportTests = function(){
- var div = document.createElement('div'),
- doc = document,
- view,
- last;
-
- div.innerHTML = '<div style="height:30px;width:50px;"><div style="height:20px;width:20px;"></div></div><div style="float:left;background-color:transparent;">';
- doc.body.appendChild(div);
- last = div.lastChild;
-
- if((view = doc.defaultView)){
- if(view.getComputedStyle(div.firstChild.firstChild, null).marginRight != '0px'){
- supports.correctRightMargin = false;
- }
- if(view.getComputedStyle(last, null).backgroundColor != 'transparent'){
- supports.correctTransparentColor = false;
- }
- }
- supports.cssFloat = !!last.style.cssFloat;
- doc.body.removeChild(div);
- };
-
- if (Ext.isReady) {
- supportTests();
- } else {
- Ext.onReady(supportTests);
- }
-})();
-
-
-<div id="cls-Ext.EventObject"></div>/**
- * @class Ext.EventObject
- * Just as {@link Ext.Element} wraps around a native DOM node, Ext.EventObject
- * wraps the browser's native event-object normalizing cross-browser differences,
- * such as which mouse button is clicked, keys pressed, mechanisms to stop
- * event-propagation along with a method to prevent default actions from taking place.
- * <p>For example:</p>
- * <pre><code>
-function handleClick(e, t){ // e is not a standard event object, it is a Ext.EventObject
- e.preventDefault();
- var target = e.getTarget(); // same as t (the target HTMLElement)
- ...
-}
-var myDiv = {@link Ext#get Ext.get}("myDiv"); // get reference to an {@link Ext.Element}
-myDiv.on( // 'on' is shorthand for addListener
- "click", // perform an action on click of myDiv
- handleClick // reference to the action handler
-);
-// other methods to do the same:
-Ext.EventManager.on("myDiv", 'click', handleClick);
-Ext.EventManager.addListener("myDiv", 'click', handleClick);
- </code></pre>
- * @singleton
- */
-Ext.EventObject = function(){
- var E = Ext.lib.Event,
- clickRe = /(dbl)?click/,
- // safari keypress events for special keys return bad keycodes
- safariKeys = {
- 3 : 13, // enter
- 63234 : 37, // left
- 63235 : 39, // right
- 63232 : 38, // up
- 63233 : 40, // down
- 63276 : 33, // page up
- 63277 : 34, // page down
- 63272 : 46, // delete
- 63273 : 36, // home
- 63275 : 35 // end
- },
- // normalize button clicks
- btnMap = Ext.isIE ? {1:0,4:1,2:2} : {0:0,1:1,2:2};
-
- Ext.EventObjectImpl = function(e){
- if(e){
- this.setEvent(e.browserEvent || e);