AriaRoleSupport#ariaRole

ariaRoleStringpublic Defined in packages/ember-views/lib/mixins/aria_role_support.js:14 The WAI-ARIA role of the control represented by this view. For example, a button may have a role of type 'button', or a pane may have a role of type 'alertdialog'. This property is used by assistive software to help visually challenged users navigate rich web applications. The full list of valid WAI-ARIA roles is available at: http://www.w3.org/TR/wai-aria/roles#roles_categorization Default: null

AriaRoleSupport

Ember.AriaRoleSupport Class PRIVATE Defined in: packages/ember-views/lib/mixins/aria_role_support.js:8 Module: ember-views

Applications and Instances

Applications and Instances Every Ember application is represented by a class that extends Ember.Application. This class is used to declare and configure the many objects that make up your app. As your application boots, it creates an Ember.ApplicationInstance that is used to manage its stateful aspects. This instance acts as the "owner" of objects instantiated for your app. Essentially, the Application defines your application while the ApplicationInstance manages its state. This separation o

ApplicationInstance.BootOptions#shouldRender

shouldRenderbooleanpublic Defined in packages/ember-application/lib/system/application-instance.js:376 Disable rendering completely. When this flag is set to true, it will disable the entire rendering pipeline. Essentially, this puts the app into "routing-only" mode. No templates will be rendered, and no Components will be created. Default: true

ApplicationInstance.BootOptions#rootElement

rootElementString|Elementpublic Defined in packages/ember-application/lib/system/application-instance.js:426 If present, overrides the application's rootElement property on the instance. This is useful for testing environment, where you might want to append the root view to a fixture area. In non-browser mode, because Ember does not have access to jQuery, this options must be specified as a DOM Element object instead of a selector string. See the documentation on Ember.Applications's rootEl

ApplicationInstance.BootOptions#location

locationstringpublic Defined in packages/ember-application/lib/system/application-instance.js:451 If present, overrides the router's location property with this value. This is useful for environments where trying to modify the URL would be inappropriate. Default: null

ApplicationInstance.BootOptions#jQuery

jQueryObjectprivate Defined in packages/ember-application/lib/system/application-instance.js:315 Provide a specific instance of jQuery. This is useful in conjunction with the document option, as it allows you to use a copy of jQuery that is appropriately bound to the foreign document (e.g. a jsdom). This is highly experimental and support very incomplete at the moment. Default: auto-detected

ApplicationInstance.BootOptions#isInteractive

isInteractivebooleanprivate Defined in packages/ember-application/lib/system/application-instance.js:329 Interactive mode: whether we need to set up event delegation and invoke lifecycle callbacks on Components. Default: auto-detected

ApplicationInstance.BootOptions#isBrowser

isBrowserbooleanpublic Defined in packages/ember-application/lib/system/application-instance.js:340 Run in a full browser environment. When this flag is set to false, it will disable most browser-specific and interactive features. Specifically: It does not use jQuery to append the root view; the rootElement (either specified as a subsequent option or on the application itself) must already be an Element in the given document (as opposed to a string selector). It does not set up an EventDisp

ApplicationInstance.BootOptions#document

documentDocumentpublic Defined in packages/ember-application/lib/system/application-instance.js:399 If present, render into the given Document object instead of the global window.document object. In practice, this is only useful in non-browser environment or in non-interactive mode, because Ember's jQuery dependency is implicitly bound to the current document, causing event delegation to not work properly when the app is rendered into a foreign document object (such as an iframe's contentDo