Timeline for A directive allowing to make a whole DOM subtree readonly
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 10, 2015 at 0:29 | vote | accept | maaartinus | ||
| Aug 15, 2014 at 5:19 | comment | added | maaartinus |
I couldn't get it working and now I know why: At the enclosing element, I'm using ng-readonly which adds the readonly attribute later. And I know now, why I don't like using a scope variable: There are two parts of the form, each of them dependent on its own expression. Expressing this in the DOM is trivial, expressing it on every input is ugly, and having two different $scope.is_readonly would be even uglier. But maybe creating a scope for each part is the way to go?
|
|
| Jul 28, 2014 at 16:19 | history | bounty ended | maaartinus | ||
| Jul 24, 2014 at 1:19 | comment | added | maaartinus |
I disagree with the scope variable proposal (see my updated question), but I like the idea using require. I'll try to get it working.
|
|
| Jul 24, 2014 at 0:41 | history | answered | Thomas | CC BY-SA 3.0 |