Thanks Zlatko and Sander for replying,
I have created a workaround for this,
Instead of using disable when in ng-repeat, I have used ng-change and
ng-disable, now it's working fine.
On Saturday, October 27, 2018 at 10:44:45 PM UTC+5:30, Sander Elias wrote:
>
> Hi Arun,
>
> What Zlatko said,
Hi Arun,
What Zlatko said, Also search this group, I'm pretty sure I created exactly
this thing before it was added to angular.
Regards
Sander
--
You received this message because you are subscribed to the Google Groups
"Angular and AngularJS discussion" group.
To unsubscribe from this group
Not a workaround, but a solution. If you don't want to upgrade angular to a
version that has this feature, you have to implement the feature yourself. So
you can tell the management in the company that upgrading angular costs X, and
developing just this feature costs Y. It's quite likely that Y
Hi sander,
I can't upgrade to newer version, the company I am working, they are using
older version they won't upgrade whole application for a single enhancement.
Any workaround on using 'disable when' in ng-repeat ?
On Friday, October 26, 2018 at 8:25:25 PM UTC+5:30, Sander Elias wrote:
>
> Hi
Hi Arun,
By backporting all the fixes from 1.5 to 1.1.
Is there a reason you can't upgrade to a newer version?
Regards
Sandeer
--
You received this message because you are subscribed to the Google Groups
"Angular and AngularJS discussion" group.
To unsubscribe from this group and stop
