ng-enabled

[cricardol]

Should this attribute be created in a future release?

[mhevery]

what is the rationalization?

On Fri, Aug 10, 2012 at 7:01 AM, cric notifications@github.com wrote:

Should this attribute be created in a future release?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/1252.

[andershessellund]

You need to use ng-disabled - there is no HTML attribute called enabled.

[adz]

It should be added for completeness...

Why have both ng-show and ng-hide when you can just use ng-hide?

It sometimes reads better, just like the show/hide variants, by avoiding double negatives:
<button ng-enabled='loaded && product.available'/>

Vs:
<button ng-disabled='!(loaded && product.available)'/>

[pierredewilde]

+1

[graphnode]

+1

I have a function in this attribute. It confused the hell of me that I need to return true to disable the button.

[perrygovier]

+1

[rzschech]

+1

[wokier]

as @adz said, like ng-show and ng-hide

[shangxiao]

+1 as it makes for better readability - an ng-enabled would eliminate double negatives

[bevacqua]

+1 👍

[mmastrac]

+1 as well. I spent a few minutes today wondering why my ng-enabled="blah" directive wasn't working before I realized that there wasn't one.

[devmondo]

👍

[pencilcheck]

+1 Come on guys, you can make it