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 a keypress event deletes an element, a rapid subsequent keypress may fire on the element before it is deleted, rather than on the replacement element which really should handle it. The OnWebsocketRecieve handler thus would get an "id not found". For now we are simply ignoring this keypress event, which may be an OK solution. For automated testing though, this probably will not work. We may need a delay or a new solution of some sort.
The text was updated successfully, but these errors were encountered:
When a keypress event deletes an element, a rapid subsequent keypress may fire on the element before it is deleted, rather than on the replacement element which really should handle it. The OnWebsocketRecieve handler thus would get an "id not found". For now we are simply ignoring this keypress event, which may be an OK solution. For automated testing though, this probably will not work. We may need a delay or a new solution of some sort.
The text was updated successfully, but these errors were encountered: