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.

Sign up for GitHub

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

Jump to bottom

Mix-in vs. Service: different behaviour when used in a component #82

Closed
myartsev opened this issue Dec 10, 2016 · 2 comments
Closed

Mix-in vs. Service: different behaviour when used in a component #82

myartsev opened this issue Dec 10, 2016 · 2 comments

Comments

@myartsev
Copy link

The mix-in event will fire only when the component itself is resized.
The service event will fire whenever the entire window is resized.

Is this intentional? The readme documentation makes it sound like the two are equivalent.
https://ember-twiddle.com/7ba80efb25e56c2dd7b9baa9aadec42e
@mike-north
Copy link
Owner

This is working as intended, and the main reason for the mixin to exist

mike-north pushed a commit that referenced this issue Aug 23, 2018
@semantic-release-bot
chore(release): 0.2.2 [skip ci]
eeca5b9 
## [0.2.2](v0.2.1...v0.2.2) (2018-08-23)

### Bug Fixes

* update README to clarify purpose of mixin ([b84682e](b84682e)), closes [#82](#82)
@mike-north
Copy link
Owner

🎉 This issue has been resolved in version 0.2.2 🎉

The release is available on:

Your semantic-release bot 📦🚀

@renovate renovate bot mentioned this issue Feb 22, 2020
Merged
1 task
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mike-north @myartsev