with the pull request updating here the bililiteRange library, there were some bug fixes and improvements since current version in this repository.
It also fixes the problem with the simplechar method of a keysequence: rng.text method reapplies the text value of the element and thats why the .selectionStart is dropped to the end, though the bililiteRange tracks the bounds internal, the problem occures when triggering afterwards the keyup event, this makes billiteRange to recalculate bounds and then all further characters are appended to the end.
Hi Jochen,
with the pull request updating here the bililiteRange library, there were some bug fixes and improvements since current version in this repository. It also fixes the problem with the
simplechar
method of a keysequence:rng.text
method reapplies the text value of the element and thats why the.selectionStart
is dropped to the end, though thebililiteRange
tracks the bounds internal, the problem occures when triggering afterwards thekeyup
event, this makesbilliteRange
to recalculate bounds and then all further characters are appended to the end.