You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 13, 2018. It is now read-only.
If too many element selections are changed even while the older element's O.o() listeners are removed, or while object-tree is being populated, unexpected things may happen.
#28
Open
sachinhosmani opened this issue
Jul 24, 2014
· 1 comment
It may take some time to load an object and a model object into the object-trees.
So it makes sense to have a state that prevents further element selections while this happens. Maybe it could look at pending selections after it finishes dealing with the current one.
(like how it is done with DOM mutations now)
The text was updated successfully, but these errors were encountered:
It may take some time to load an object and a model object into the object-trees.
So it makes sense to have a state that prevents further element selections while this happens. Maybe it could look at pending selections after it finishes dealing with the current one.
(like how it is done with DOM mutations now)
The text was updated successfully, but these errors were encountered: