-
Notifications
You must be signed in to change notification settings - Fork 124
Disabling seems to be totally broken except by adding disabled
attribute
#80
Comments
Just pulled down the project and discovered a test relating to this failing on all browsers:
|
I did a git bisect, and discovered the commit where this test started failing:
|
I fix the issue, it works with ng-disabled
|
@darksonwolf any chance of creating a Pull request for that? I want to see this fix implemented if it works as advertised. I see you have a fork, but don't see this commit there? |
Any progress on this? Any known workarounds? |
perhaps @darksonwolf's code above works? Maybe someone could check it out and submit a PR? I'd like to see this working myself... Any thoughts @cgarvis ? |
PRs are most welcomed |
i just created a pull request (#87) for this issue. |
Any release date for the pull request? |
Would also like to see this implemented? |
Any release date for the pull request? :( |
It seems that the only way to toggle disabling of this directive is to add or remove the
disabled
attribute manually (at least in Chrome/OSX).ng-disabled
does not seem to work at all.I forked @zauker's demo from Issue #78 which should make any issues clear.
http://plnkr.co/edit/YtlRjooAZiiv0uAN3a5G?p=preview
The text was updated successfully, but these errors were encountered: