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
When calling destroy or destroyAll then ptrElement might become visible for a short period of time when its styleEl is messed up (see #119) due to it not getting removed from DOM immediately.
Current behavior:
When calling handler's destroy function then it does not remove ptrElement. It is being removed by onReset which might be called from multiple codepaths. However, in onReset a timeout is being used which in turn might cause a situation where ptrElement is removed from DOM after its handler's destroy has been called many cycles ago (default removal timeout is 500ms for example).
Expected behavior:
ptrElement should be removed immediately when _handler.destroy is been executed to avoid possible problems where handler has been destroyed and its element will be removed later by co-incidence by some timer.
JSFiddle URL for demo with bug:
N/A
Browsers affected:
Every browser
The text was updated successfully, but these errors were encountered:
Bug report
When calling
destroy
ordestroyAll
thenptrElement
might become visible for a short period of time when itsstyleEl
is messed up (see #119) due to it not getting removed from DOM immediately.Current behavior:
When calling handler's
destroy
function then it does not removeptrElement
. It is being removed byonReset
which might be called from multiple codepaths. However, inonReset
a timeout is being used which in turn might cause a situation whereptrElement
is removed from DOM after its handler'sdestroy
has been called many cycles ago (default removal timeout is 500ms for example).Expected behavior:
ptrElement
should be removed immediately when_handler.destroy
is been executed to avoid possible problems where handler has been destroyed and its element will be removed later by co-incidence by some timer.JSFiddle URL for demo with bug:
N/A
Browsers affected:
Every browser
The text was updated successfully, but these errors were encountered: