domRead() and domWrite() callbacks are getting called even if the scope was destroyed

[isoos]

If the component registers domRead and domWrite callbacks, yet a parent ng-if will wipe out the scope, the callbacks may find an inconsistent state. There are two outcomes here:

• calling the callbacks may cause exceptions due to the unexpected state
• not calling the callbacks may leave something else in a hanging state

I'd vote for the not calling (as potentially hanging state seems to be less frequent thing, and it is easy to handle it on a scope destroy at the first place).

[mvuksano]

I think, when destroying the scope, we should destroy it only after everything that is scheduled is executed.

[vsavkin]

@istvan-soos Misko asked me to work on it. Hopefully will be done in a few weeks.

[vsavkin]

PR #1341 closes this issue. Now it is possible to use any scope (not just the root) to schedule a dom write/read. So the component should use its scope. If that scope gets destroyed, none of the DOM operations scheduled on that scope gets executed.