Skip to content
This repository has been archived by the owner on Apr 12, 2024. It is now read-only.

Form leak fix #4779

Closed
wants to merge 3 commits into from
Closed

Form leak fix #4779

wants to merge 3 commits into from

Conversation

IgorMinar
Copy link
Contributor

No description provided.

Due to animations, DOM might get destroyed much later than scope and so the element $destroy event
might get fired outside of $digest, which causes changes to the validation model go unobserved
until the next digest. By deregistering on scope  event, the deregistration always happens
in $digest and the form validation model changes will be observed.

Closes angular#4226
Closes angular#4779
@btford
Copy link
Contributor

btford commented Nov 4, 2013

LGTM

@IgorMinar IgorMinar closed this in 8f989d6 Nov 4, 2013
jamesdaily pushed a commit to jamesdaily/angular.js that referenced this pull request Jan 27, 2014
Due to animations, DOM might get destroyed much later than scope and so the element $destroy event
might get fired outside of $digest, which causes changes to the validation model go unobserved
until the next digest. By deregistering on scope  event, the deregistration always happens
in $digest and the form validation model changes will be observed.

Closes angular#4226
Closes angular#4779
jamesdaily pushed a commit to jamesdaily/angular.js that referenced this pull request Jan 27, 2014
Due to animations, DOM might get destroyed much later than scope and so the element $destroy event
might get fired outside of $digest, which causes changes to the validation model go unobserved
until the next digest. By deregistering on scope  event, the deregistration always happens
in $digest and the form validation model changes will be observed.

Closes angular#4226
Closes angular#4779
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants