Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ensure view-registry is injected for unit tested components. #92

Conversation

rwjblue
Copy link
Member

@rwjblue rwjblue commented Jul 30, 2015

Fixes #91.

In Ember 1.12.0 and 1.12.1 the `-view-registry:main` was introduced as a
mechanism to track views without mutating the global `Ember.View.views`
registry (needed for fastboot work), unfortunately the
`Ember.EventDispatcher` was not updated to use the new view registry and
therefore any views added in a view registry other than
`Ember.View.views` will not be able to handle DOM events. The event
dispatcher was fixed in emberjs/ember.js#11290.

This change ensures that `-view-registry:main` is the same as
`Ember.View.views` on Ember versions where `Ember.View.views` exists
(Ember < 1.13.0).
@rwjblue rwjblue force-pushed the ensure-view-registry-exists-for-component-unit-tests branch from 4b053d1 to bec1ba6 Compare July 30, 2015 20:00
rwjblue added a commit that referenced this pull request Jul 30, 2015
…omponent-unit-tests

Ensure view-registry is injected for unit tested components.
@rwjblue rwjblue merged commit abf4d94 into emberjs:master Jul 30, 2015
@rwjblue rwjblue deleted the ensure-view-registry-exists-for-component-unit-tests branch July 30, 2015 20:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant