execCommand('inserttext',...) behavior

I have a question about space canonicalization that happens in the browser when an user inserts or removes text or when it is done through execCommand(‘inserttext’,...). Spec: https://w3c.github.io/editing/execCommand.html#canonical-space-sequences – section 9.7.

I’ve been investigating what happens in Chrome when we have a situation with multiple spaces in the string: ‘ foo bar ‘.

It seems that there is a bug in Chrome. I was not able to investigate what happens in Firefox as I couldn’t see insertion of &nbsp in Firefox console. Not sure if Firefox is inserting it but it is not displayed in the console or like Edge, they are not doing it.

Chrome folks: this looks like a bug

Here is the sample: https://jsfiddle.net/mwvywtze/ .

Expected output:

some text  foo  bar  

Actual output:

some text  foo bar  

thanks,
--grisha

Start with section 9.7 of the linked execCommand specification and reproduce the behavior using the provided JSFiddle. Compare Chrome's output with the expected canonical space sequence and investigate the corresponding behavior in Firefox or Edge. Done means determining whether the result violates the specification and documenting the confirmed browser behavior or required specification clarification.