Fix typo
[DOC beta] Document Ember.Route #controllerName and #viewName properties.
[BUGFIX beta] Remove false attribute from Ember.View

In IE8 (or older), `jQuery.fn.prop` always update DOM against our
expectation.(This is a jQuery bug but it couldn't fix)
ref: http://bugs.jquery.com/ticket/13558

So the following test is failed due to `view.$().attr('foo')` returns `"false"`.:
* https://github.com/emberjs/ember.js/blob/a449d445/packages/ember-views/tests/views/view/attribute_bindings_test.js#L126

To avoid this issue, `removeAttr` should be called when `null`, `undefined` or `false` is given as value.

But this way contains incompatible changes:

Before:
``` javascript
view.set('checked', false);
view.$().prop('checked'); //=> false
```

After:
``` javascript
view.set('checked', false);
view.$().prop('checked'); //=> undefined
```
Don't call toString at extend time

Doing so will memoize the function so that any Ember.View subclass will return the same value for toString.
[BUGFIX beta] Allow Ember.computed.sort to use property paths in sortDefinitions.

'Ember.computed.sort' 'works only if sortDefinitions contain simple properties.
It will fail if a `sortDefinition` contains a property path (i.e. something
like `person.name`).

A `SearchProxy` is used to shadow the new value of an underlying property with
the old value to ensure proper comparisons take place while searching for an
item in the sorted array. When using a property path rather than a simple
property to sort on, `SearchProxy` will use the actual property path in its
attempt to shadow underlying properties - something like: `{ person.name: 'John
Doe' }`. This causes things to blow up because every comparison between an
existing item `get(itemA, sortProperty)` and a SearchProxy `get(itemB,
sortProperty)` will return a bogus result. In this case, `get(itemB,
'person.name')` will not return the shadowed value (stored as `{ person.name:
'John Doe' } `) but rather the current value of that path on the proxy's
underlying `content`.

This commit allows a proper comparison to take place when a sortDefinition
contains a property path.
remove unneeded get
we now have multi-line asserts, lets use them!
[BUGFIX beta] Better error for content set on object
Merge pull request #4066 from tricknotes/fix-to-remove-attrs

[BUGFIX beta] Remove false attribute from Ember.View for IE8
Remove `Ember.handleErrors`
Merge pull request #3940 from sandstrom/handle-errors

Remove `Ember.handleErrors`
[SECURITY CVE-2014-0014] Ensure {{group}} helper escapes properly.

This vulnerability has been assigned the CVE identifier CVE-2014-0014.

In general, Ember.js escapes or strips any user-supplied content before
inserting it in strings that will be sent to innerHTML.  However, we
have identified a vulnerability that could lead to unescaped content being
inserted into the innerHTML string without being sanitized.

When using the `{{group}}` helper, user supplied content in the template
was not being sanitized. Though the vulnerability exists in Ember.js proper,
it is only exposed via the use of an experimental plugin.

In applications that use the `{{group}}` helper, a specially-crafted
payload could execute arbitrary JavaScript in the context of the current
domain ("XSS").

This vulnerability was reported to us by Edward Faulkner of CleriCare.
Many thanks for working with us on the patches and advisory.
[SECURITY CVE-2014-0013] Ensure primitive value contexts are escaped.

This vulnerability has been assigned the CVE identifier CVE-2014-0013.

In general, Ember.js escapes or strips any user-supplied content before
inserting it in strings that will be sent to innerHTML.  However, we have
identified a vulnerability that could lead to unescaped content being inserted
into the innerHTML string without being sanitized.

When a primitive value is used as the Handlebars context, that value is not
properly escaped.  An example of this would be using the `{{each}}` helper to
iterate over an array of user-supplied strings and using `{{this}}` inside the
block to display each string.

In applications that contain templates whose context is a primitive value and
use the `{{this}}` keyword to display that value, a specially-crafted payload
could execute arbitrary JavaScript in the context of the current domain
("XSS").

This vulnerability was discovered by Robert Jackson of DockYard. Many
thanks for working with us on the patches and advisory.
Refactor sanitization into reusable function.
Update CHANGELOG.
Add missing entries to CHANGELOG.
Remove unused variable
Merge pull request #4153 from mjijackson/remove-unused-var

Remove unused variable
Add Ember.setupForTesting.

This makes it somewhat easier to unit-test Ember. It also gives us a
good place to add additional customization (as opposed to advocating
simply setting `Ember.testing = true`).
Add missing links to FEATURES.md.