Enter after the end of the text doesn't work the first time about dabblet HOT 6 CLOSED

It seems that the semicolon isn't the crucial to reproduce.

It reproduced to me when you press enter after some symbols at the end of block with contenteditable and there were no whitespaces at the start of the line.

So, in empty pane writing something (without spaces/tabs at start) in the first line and pressing enter would reproduce the bug.

Also, there is a bug that relates to this: when you're on the last line and didn't press the enter for the first time, them deleting everything in this line would place the caret at the beginning of code block.

So, after writing a+enter+enter+b you could see the following (“|” is a caret):

a
b|

Then pressing backspace the b would be deleted, but the caret would be moved to the start:

|a

But if you'd press the enter after b (which won't create a new line), then pressing backspace wouldn't move the caret.

from dabblet.

Also, I saw that this behavior can be seen both in Chrome/Safari and in Firefox, but in Firefox this works another way: when you press enter for the first time, you don't see the newline, but when you press any other key (chars, or enter again), you'd see that there were a new line, so pressing enter two times would create two line breaks (and only one in webkits).

from dabblet.

It seems this only happens when the caret is at the end of the text. Can anyone reproduce in other cases?

from dabblet.

Only at the end of text to me too. In other cases it was ok every time I've tested.

from dabblet.

I think I fixed it, although in a way I'm not too proud of. Can you confirm please?

from dabblet.

Works for me now.

from dabblet.