input[checkbox] doesn't catch checked in scope directive

[reivaxm]

The attribute "checked" is not recovered in the scope of a directive.
This seems broken since version 1.4.4
https://plnkr.co/edit/0j7Y9mkeP4m2waCLYLxU?p=preview
Working on 1.3.15
https://plnkr.co/edit/GN4K5EdtfHxPpe7x3OCc?p=preview

[Narretz]

Seems to have been caused by 6f3b862 in combination with replace: true (if you remove replace, it works). Since replace is deprecated, I wouldn't hold out for a fix. If you want to provide a PR that fixes it, I'll be happy to take a look.

[Narretz]

Oh, i also works if you use a different name for the checked attribute: https://plnkr.co/edit/yHiTck5stWNkhASsWA7t?p=preview
It's possible that checked is somehow special cased by the browser.

[petebacondarwin]

The problem is that checked is a BOOLEAN attribute and Angular is converting it to a boolean value rather than leaving it as a string...

[petebacondarwin]

This is the relevant commit: 8a1eb16

[petebacondarwin]

So since we always convert boolean attributes to a boolean value, you cannot use interpolation inside them as this will always be converted to true.
A simple workaround for you @reivaxm is to use $attr in your link function and write out the scope property manually... https://plnkr.co/edit/F6s1b50tHxsl5DQkeNlw?p=preview
But I have a basic fix coming anyway...

[Narretz]

Ah, I was looking for this previous commit. Note that the plnkr only fails once you go to 1.4.4, though.

[petebacondarwin]

Well this commit was part of a bit of reverting and unreverting work at the time so it is not exactly clear where it appears

[petebacondarwin]

Here is the fix #13769
Can you take a look @Narretz ?

[reivaxm]

Thanks a lot for your reactivity, the fix and globally for your work. I'll try that tomorrow.