ng:repeat should optionally not reuse nodes

[IgorMinar]

ng:repeat does some very efficient DOM manipulation, but all of these tricks are not suitable for some use cases, e.g.:

• apps that do extra dom manipulation for repeated nodes that ng:repeat doesn't know about
• apps that would like to animate reordering of data (and nodes)

when ng:repeat notices that the model changed and that there are more or fewer elements in the repeated collection, then it just adds the required number of new nodes or throws away the required number of nodes and reuses the remaining ones by just simply updating the data bindings. this means that all the extra DOM stuff that it doesn't know about gets lost or associated with wrong node.

we should have a way to tell ng:repeat that this behavior is not desirable and that it should be less efficient but more friendly towards this extra dom manipulation.

here is one test case that is broken due to the current behavior of ng:repeat: http://jsfiddle.net/gronky/XsHqL/

[IgorMinar]

After a long discussion we decided to mark this issue as wontfix. For more details please see the commit message for a related issue.

3ea2416