-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
[1.13.0 Regression] Views doesn't use attributeBindings #11480
Comments
Confirmed that |
@rwjblue here's a JSBin demo |
I do not suggest using an |
Any progress on this issue? |
Same issue here on Ember 1.13.9: I have a component like such: export default Ember.Component.extend({
tagName: 'a',
href: '#',
id: 'my-component',
attributeBindings: ['href', 'id'],
click: function(event) {
event.preventDefault();
console.log("CLICK");
}
} Interestingly, the |
Ah, I get what's happening here. Just to make sure it wasn't related to the concatenatedProperties bug resolved in 1.13.10, I upgraded. Same problem. But when you attributeBind to Is there a workaround for this or more relevant issue? |
The demo JSBin seems to be working properly on release-1-13 branch: http://emberjs.jsbin.com/tufosiz/edit?js,output. |
Was fixed in #11889. |
#11889 did fix not being able to bind to Try adding a "click" handler to your example (e.g. an alert) and notice it doesn't fire when attributeBindings includes |
it appears you can get around this bug by binding like this
|
Seems fixed in 2.12 (Ember-Twiddle). Closing this. Thank you everyone! |
Hello, I have been using attributeBindings: ['id'] in order to assign id to my route's view. This way I can "namespace" css by route. This has stopped working since 1.13.0 (same as in components). I understand the reasons here #11141 , but it's not valid for a routes view, since it's not written in templates. Am I not folliwing the "right way" or it's really a regression (please feel free to replace the title if not)? Thanks!
The text was updated successfully, but these errors were encountered: