The final space is `nbsp` (ascii 160), internal spaces are ascii 20

[rcoh]

if you type a b and call editorState.getCurrentContent().getPlainText() the internal space is a normal space but the final space is ascii 160. This causes problems if you want to match this text against other strings. I fixed it externally with the code below, but maybe this fix should be handled internally?

  cleanPlainText(editorState) {
    const text = editorState.getCurrentContent().getPlainText();
    const nbsp = String.fromCharCode(160);
    const regex = new RegExp(`${nbsp}`, 'g');
    return text.replace(regex, ' ');
  },

[hellendag]

Hmm, this doesn't repro for me. You've typed a, ,b, correct? I'm not sure why there would be an  there as well.

[rcoh]

There is a space after the b and that's the one that comes out as the incorrect ascii code. I'll see if I can make a tester tonight.

[hellendag]

Ah, so you typed a, ,b, ? And the two spaces are not the same character?

[rcoh]

exactly

[hellendag]

Which browser and OS?

[rcoh]

chrome 48.0.2564.109, OS X 10.11.2,

If it isn't reproducing elsewhere, perhaps it's a weird artifact of how I was using the control.

[hellendag]

Are you able to determine whether the space bar character insertions are occurring via editOnBeforeInput?

[hellendag]

@rcoh just wanted to follow up on this. I haven't seen this issue before, but I'd certainly like to fix it if it's widespread.

[MindRave]

@hellendag I think I'm seeing the same thing here. Chrome 48.0.2564.116 (64-bit), OSX 10.11.2. The last space is an &nbsp for me as well.

EDIT:
Also tested in Safari, just in case. Not seeing the issue. Probably just Chrome.

[hellendag]

You didn't type that with an option+spacebar, right? Just regular spaces?

[MindRave]

Yes, just regular spaces.

[hellendag]

If you add more spaces, does it add more   characters? Or does that one continue to stick to the end of the text node?

Also, are you using any Chrome extensions?

[MindRave]

It doesn't add more   characters if I add more spaces, that one continues to stick to the end of the node, yes.

I am (quite a few), but I disabled all of them, shut Chrome down and retested. Same thing.