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
This issue is similar to #6: Sometimes, when simulating a key sequence with delay in a non-input element in IE (>= 11?), spaces in the sequence delete the contents of the element.
For example:
After calling
$('#myDiv').simulate('key-sequence', {sequence: 'my little text', delay: 100});
#myDiv contains text, but it can be seen that the rest of the sequence is simulated as well, but each space removes the current content of the div. This even happens with the \xA0 character.
I haven't found out in which situations this problem occurrs but it doesn't seem to be related to the visibility of the element. Chances are good that the problem come from bililiteRange.js in combination with IEs implementation of the Range API.
This issue is similar to #6: Sometimes, when simulating a key sequence with delay in a non-input element in IE (>= 11?), spaces in the sequence delete the contents of the element.
For example:
After calling
#myDiv
containstext
, but it can be seen that the rest of the sequence is simulated as well, but each space removes the current content of the div. This even happens with the\xA0
character.I haven't found out in which situations this problem occurrs but it doesn't seem to be related to the visibility of the element. Chances are good that the problem come from bililiteRange.js in combination with IEs implementation of the Range API.
The fix from #6 doesn't solve this problem.
The text was updated successfully, but these errors were encountered: