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

[BUGFIX beta] Prevent classNames from being duplicated. #12184

Merged
merged 2 commits into from
Aug 23, 2015

Conversation

rwjblue
Copy link
Member

@rwjblue rwjblue commented Aug 23, 2015

When a component is created we pass all attrs as root properties. In this case, that means that the classNames concatenated properties have already been merged/handled.

The fix is to remove the processing of attrs.classNames from normalizeClass, which prevents any classes provided via classNames from being added twice.

Closes #11609.
Fixes #11600.
Fixed #12146.

fpauser and others added 2 commits August 23, 2015 08:55
When a component is created we pass all `attrs` as root properties. In
this case, that means that the `classNames` concatenated properties have
already been merged/handled.

The fix is to remove the processing of `attrs.classNames` from
`normalizeClass`, which prevents any classes provided via `classNames`
from being added twice.
rwjblue added a commit that referenced this pull request Aug 23, 2015
[BUGFIX beta] Prevent `classNames` from being duplicated.
@rwjblue rwjblue merged commit 3e15e67 into emberjs:master Aug 23, 2015
@rwjblue rwjblue deleted the duplicate-classes branch August 23, 2015 14:17
@Dhaulagiri
Copy link
Contributor

@rwjblue it doesn't look like this fix is included in 1.13 (see this twiddle for reproduction). Any opposition to a PR into the 1.13 branch with this change?

@rwjblue
Copy link
Member Author

rwjblue commented Jan 8, 2016

@Dhaulagiri - Correct, this PR was targeted at beta branch which at the time was 2.1.0-beta.x (and not 1.13). I'm not really opposed to backporting if it is an issue for y'all (would love a PR against release-1-13 if you have the time)...

@Dhaulagiri
Copy link
Contributor

At this point it is more confusing to see than an actual problem. It'll only take a couple of minutes to cherry pick these commits, so I'll probably do it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants