Class Ember.TextArea

The internal class used to create textarea element when the {{textarea}} helper is used.

See handlebars.helpers.textarea for usage details.

Layout and LayoutName properties

Because HTML textarea elements do not contain inner HTML the layout and layoutName properties will not be applied. See Ember.View's layout section for more information.

Show:

Module: ember

The action to be sent when the user presses the return key.

This is similar to the {{action}} helper, but is fired when the user presses the return key when editing a text field, and sends the value of the field as the context.

Module: ember

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

Module: ember

A list of properties of the view to apply as attributes. If the property is a string value, the value of that string will be applied as the attribute.

1
2
3
4
5
6
// Applies the type attribute to the element
// with the value "button", like <div type="button">
Ember.View.extend({
  attributeBindings: ['type'],
  type: 'button'
});

If the value of the property is a Boolean, the name of that property is added as an attribute.

1
2
3
4
5
// Renders something like <div enabled="enabled">
Ember.View.extend({
  attributeBindings: ['enabled'],
  enabled: true
});
Module: ember

Whether they keyUp event that triggers an action to be sent continues propagating to other views.

By default, when the user presses the return key on their keyboard and the text field has an action set, the action will be sent to the view's controller and the key event will stop propagating.

If you would like parent views to receive the keyUp event even after an action has been dispatched, set bubbles to true.

Module: ember

A list of properties of the view to apply as class names. If the property is a string value, the value of that string will be applied as a class name.

1
2
3
4
5
// Applies the 'high' class to the view element
Ember.View.extend({
  classNameBindings: ['priority']
  priority: 'high'
});

If the value of the property is a Boolean, the name of that property is added as a dasherized class name.

1
2
3
4
5
// Applies the 'is-urgent' class to the view element
Ember.View.extend({
  classNameBindings: ['isUrgent']
  isUrgent: true
});

If you would prefer to use a custom value instead of the dasherized property name, you can pass a binding like this:

1
2
3
4
5
// Applies the 'urgent' class to the view element
Ember.View.extend({
  classNameBindings: ['isUrgent:urgent']
  isUrgent: true
});

This list of properties is inherited from the view's superclasses as well.

Module: ember

Standard CSS class names to apply to the view's outer element. This property automatically inherits any class names defined by the view's superclasses as well.

Module: ember

Defines the properties that will be concatenated from the superclass (instead of overridden).

By default, when you extend an Ember class a property defined in the subclass overrides a property with the same name that is defined in the superclass. However, there are some cases where it is preferable to build up a property's value by combining the superclass' property value with the subclass' value. An example of this in use within Ember is the classNames property of Ember.View.

Here is some sample code showing the difference between a concatenated property and a normal one:

1
2
3
4
5
6
7
8
9
10
11
12
13
App.BarView = Ember.View.extend({
  someNonConcatenatedProperty: ['bar'],
  classNames: ['bar']
});

App.FooBarView = App.BarView.extend({
  someNonConcatenatedProperty: ['foo'],
  classNames: ['foo'],
});

var fooBarView = App.FooBarView.create();
fooBarView.get('someNonConcatenatedProperty'); // ['foo']
fooBarView.get('classNames'); // ['ember-view', 'bar', 'foo']

This behavior extends to object creation as well. Continuing the above example:

1
2
3
4
5
6
var view = App.FooBarView.create({
  someNonConcatenatedProperty: ['baz'],
  classNames: ['baz']
})
view.get('someNonConcatenatedProperty'); // ['baz']
view.get('classNames'); // ['ember-view', 'bar', 'foo', 'baz']

Adding a single property that is not an array will just add it in the array:

1
2
3
4
var view = App.FooBarView.create({
  classNames: 'baz'
})
view.get('classNames'); // ['ember-view', 'bar', 'foo', 'baz']

Using the concatenatedProperties property, we can tell to Ember that mix the content of the properties.

In Ember.View the classNameBindings and attributeBindings properties are also concatenated, in addition to classNames.

This feature is available for you to use throughout the Ember object model, although typical app developers are likely to use it infrequently.

Module: ember

The object from which templates should access properties.

This object will be passed to the template function each time the render method is called, but it is up to the individual function to decide what to do with it.

By default, this will be the view's controller.

Module: ember

The controller managing this view. If this property is set, it will be made available for use by the template.

Module: ember

Returns the current DOM element for the view.

Module: ember

Destroyed object property flag.

if this property is true the observers and bindings were already removed by the effect of calling the destroy() method.

Module: ember

Destruction scheduled flag. The destroy() method has been called.

The object stays intact until the end of the run loop at which point the isDestroyed flag is set.

Module: ember

concatenatedProperties: ['classNames', 'classNameBindings', 'attributeBindings'], /**

Module: ember

If false, the view will appear hidden in DOM.

Module: ember

A view may contain a layout. A layout is a regular template but supersedes the template property during rendering. It is the responsibility of the layout template to retrieve the template property from the view (or alternatively, call Handlebars.helpers.yield, {{yield}}) to render it in the correct location.

This is useful for a view that has a shared wrapper, but which delegates the rendering of the contents of the wrapper to the template property on a subclass.

Module: ember

The name of the layout to lookup if no layout is provided.

Ember.View will look for a template with this name in this view's templates object. By default, this will be a global object shared in Ember.TEMPLATES.

Module: ember
returns
Ember.View

Return the nearest ancestor whose parent is an instance of klass.

Module: ember
returns
Ember.View

Return the nearest ancestor that is an instance of the provided class or mixin.

Module: ember
returns
Ember.View

Return the nearest ancestor that has a given property.

Module: ember

The event that should send the action.

Options are:

  • enter: the user pressed enter
  • keypress: the user pressed a key
Module: ember

If the view is currently inserted into the DOM of a parent view, this property will point to the parent of the view.

Module: ember

Tag name for the view's outer element. The tag name is only used when an element is first created. If you change the tagName for an element, you must destroy and recreate the view element.

By default, the render buffer will use a <div> tag for views.

Module: ember

The template used to render the view. This should be a function that accepts an optional context parameter and returns a string of HTML that will be inserted into the DOM relative to its parent view.

In general, you should set the templateName property instead of setting the template yourself.

Module: ember

The name of the template to lookup if no template is provided.

Ember.View will look for a template with this name in this view's templates object. By default, this will be a global object shared in Ember.TEMPLATES.

Module: ember

The hash in which to look for templateName.

Module: ember

Global views hash