[BUG] Backspace not always captured by editor

Article

Scott Beeson · Jan 13, 2016 1m read

I was editing a comment and I hit backspace a few times until there was no text left. Subsequent backspaces will actually be interpreted by the browser as a back command.

Further investigation revealed that hitting backspace on the WYSIWYG editor when there is no contend does remove focus from the element.

Discussion (3)0

Scott Beeson · Jan 13, 2016

This seems to happen on every form. Also, once you backspace all the content you cannot get the curser back in the editor without refreshing the page.

0 0

Scott Beeson · Feb 25, 2016

This has been a huge annoyance for me. Anyone else?

0 0

Scott Beeson · Oct 11, 2016

Well Chrome now blocked Backspace for navigation, so no risk of leaving the page, but this bug still persists. If you backspace past the last character the text entry box no longer has focus.

0 0