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

Add active class in run.next instead of afterRender queue #121

Merged
merged 2 commits into from
Nov 25, 2015

Conversation

kmiyashiro
Copy link
Contributor

Currently, the active class is added at the exact same time the message is
rendered (despite the afterRender queue). This will ensure that the active
class is added 1ms after it is inserted into the DOM, thus triggering any CSS
transitions from naked to active states.

Currently, the active class is added at the exact same time the message is
rendered (despite the afterRender queue). This will ensure that the active
class is added 1ms after it is inserted into the DOM, thus triggering any CSS
transitions from naked to active states.
@poteto
Copy link
Collaborator

poteto commented Nov 25, 2015

Thanks!

poteto added a commit that referenced this pull request Nov 25, 2015
Add active class in run.next instead of afterRender queue
@poteto poteto merged commit 7372d32 into adopted-ember-addons:develop Nov 25, 2015
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.

2 participants