Ext.data.JsonP.Ext_supports({"alternateClassNames":[],"aliases":{},"enum":null,"parentMixins":[],"tagname":"class","subclasses":[],"extends":null,"uses":[],"html":"
Files
Determines information about features are supported in the current environment
\nTrue if the Array sort native method isn't bugged.
\nTrue if the Array sort native method isn't bugged.
\nTrue if the browser supports the getBoundingClientRect method on elements
\nTrue if the browser supports the getBoundingClientRect method on elements
\nTrue if document environment supports the CSS3 box-shadow style.
\nTrue if document environment supports the CSS3 box-shadow style.
\nTrue if the device supports CSS3 linear gradients
\nTrue if the device supports CSS3 linear gradients
\nTrue if document environment supports the HTML5 classList API.
\nTrue if document environment supports the HTML5 classList API.
\nTrue if the browser supports document.defaultView.getComputedStyle()
\nTrue if the browser supports document.defaultView.getComputedStyle()
\nTrue if browser support CreateContextualFragment range native methods.
\nTrue if browser support CreateContextualFragment range native methods.
\nTrue if the device supports device motion (acceleration and rotation rate)
\nTrue if the device supports device motion (acceleration and rotation rate)
\nTrue if when asking for an element's dimension via offsetWidth or offsetHeight,\ngetBoundingClientRect, etc. the browser returns the subpixel width rounded to the nearest pixel.
\nTrue if INPUT elements lose their\nselection when their display style is changed. Essentially, if a text input\nhas focus and its display style is changed, the I-beam disappears.
\n\nThis bug is encountered due to the work around in place for the RightMargin\nbug. This has been observed in Safari 4.0.4 and older, and appears to be fixed\nin Safari 5. It's not clear if Safari 4.1 has the bug, but it has the same WebKit\nversion number as Safari 5 (according to http://unixpapa.com/js/gecko.html).
\nTrue if TEXTAREA elements lose their\nselection when their display style is changed. Essentially, if a text area has\nfocus and its display style is changed, the I-beam disappears.
\n\nThis bug is encountered due to the work around in place for the RightMargin\nbug. This has been observed in Chrome 10 and Safari 5 and older, and appears to\nbe fixed in Chrome 11.
\nTrue if the browser will return the left/top/right/bottom\nposition as a percentage when explicitly set as a percentage value.
\nTrue if the browser supports mouseenter and mouseleave events
\nTrue if the browser supports mouseenter and mouseleave events
\nTrue if the browser supports the mousewheel event
\nTrue if the browser supports the mousewheel event
\nIn some browsers (IE quirks, IE6, IE7, IE9, chrome, safari and opera at the time\nof this writing) a percentage-height element ignores the horizontal scrollbar\nof its parent element. This method returns true if the browser is affected\nby this bug.
\nTrue if the browser supports the HTML5 placeholder attribute on inputs
\nTrue if the browser supports the HTML5 placeholder attribute on inputs
\nTrue if document environment supports the CSS3 pointer-events style.
\nTrue if document environment supports the CSS3 pointer-events style.
\nTrue if browser support document.createRange native method.
\nTrue if browser support document.createRange native method.
\nTrue if the device supports right margin.\nSee https://bugs.webkit.org/show_bug.cgi?id=13343 for why this is needed.
\nTrue if the BoundingClientRect is\nrotated when the element is rotated using a CSS transform.
\nTrue if the BoundingClientRect is\nrotated when the element is rotated using a CSS transform.
\nIn some browsers the right padding of an overflowing element is not accounted\nfor in its scrollWidth. The result can vary depending on whether or not\nThe element contains block-level children. This method tests the effect\nof padding on scrollWidth when there are no block-level children inside the\noverflowing element.
\n\nThis method returns true if the browser is affected by this bug.
\nTrue if the browser supports maxlength on textareas.
\nTrue if the browser supports maxlength on textareas.
\nTrue if the browser passes the \"actualLateness\" parameter to\nsetTimeout. See: https://developer.mozilla.org/en/DOM/window.setTimeout
\nIn Chrome 24.0, an RTL element which has vertical overflow positions its right X origin incorrectly.\nIt skips a non-existent scrollbar which has been moved to the left edge due to the RTL setting.
\n\nhttp://code.google.com/p/chromium/issues/detail?id=174656
\n\nThis method returns true if the browser is affected by this bug.
\nGenerates a support vector for the current browser/mode. The result can be\nadded to supportsVectors to eliminate feature detection at startup time.
\nRuns feature detection routines and sets the various flags. This is called when\nthe scripts loads (very early) and again at Ext.onReady. Some detections\nare flagged as early
and run immediately. Others that require the document body\nwill not run until ready.
Each test is run only once, so calling this method from an onReady function is safe\nand ensures that all flags have been set.
\n