Yes in our app we have a custom disabling mechanism on the directive. But
attribute disabled cannot be used because of this problem. I already solved
my problem with renaming the attribute. But Im curious about this behaviour
why is acting like this.
Dne čtvrtek 2. června 2016 12:19:39 UTC+2 Manish Pal napsal(a):
>
> The actual disabled behavior you will see, if you put disabled='true' on
> the text input, instead of the div. But putting disabled on your custom
> directive, you would need to implement the disabling of the transcluded
> content yourself.
>
> On Thursday, June 2, 2016 at 3:07:56 PM UTC+5:30, lancer enkor wrote:
>>
>> I have a simple transclude directive
>>
>> app.directive('trans', function(){
>> return {
>> restrict: 'E',
>> transclude: true,
>> scope: true,
>> template: '<div><div ng-transclude></div></div>'
>> }
>> })
>>
>> And If I use directive like this:
>>
>> <input type="text" data-ng-model="data.test" placeholder="outside" />
>> <trans disabled="true">
>> <input type="text" data-ng-model="data.test" placeholder="inside" />
>> </trans>
>>
>> Then behaviour is acting different on IE11 and Chrome.
>>
>>
>> In chrome disabled is ignored.
>>
>>
>> In IE field looks like disabled but you can type in it and placeholder is
>> preserved and you cannot use delete button, only backspace.
>>
>>
>> My question is why ? And what behaviour is correct ? Is it bug in Angular
>> or in IE or in Chrome ?
>>
>>
>> Thank you
>>
>> example: https://plnkr.co/edit/DRzrXABCQheQEpa51dJj?p=preview
>>
>
--
You received this message because you are subscribed to the Google Groups
"AngularJS" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/angular.
For more options, visit https://groups.google.com/d/optout.
