no we need to keep this because the contenteditable element actually adds nonbreaking spaces when the user type manual adjacent spaces, and we need to handle this situation in `getContent`. This test ensures this.

I think the contenteditable property behaves like this because a contenteditable element does not necessarily have `white-space: pre-wrap` so it must just work in all situations.