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 a failing test that checks if classNames in DOM reflect the compo… #11609

Closed

Conversation

fpauser
Copy link
Contributor

@fpauser fpauser commented Jul 1, 2015

…nents classNames

Failing test for #11600

@rwjblue
Copy link
Member

rwjblue commented Jul 1, 2015

Awesome, thank you for the failing test!

@fpauser fpauser force-pushed the passing-classnames-to-components branch from 749c2da to bcb986d Compare July 2, 2015 19:55
@rwjblue
Copy link
Member

rwjblue commented Aug 17, 2015

This should have been fixed by #12073, can you rebase to confirm this is passing?

@fpauser fpauser force-pushed the passing-classnames-to-components branch from bcb986d to 89ca6d3 Compare August 18, 2015 15:10
@fpauser
Copy link
Contributor Author

fpauser commented Aug 18, 2015

I moved my failing test to the 'component - invocation' integration test - it's still failing.

As the test shows the classNames are properly concatenated - but there is still a duplicate class in the DOM. Seems like this is more related to concatenated properties 'serialized' to DOM?

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