Re: [w3c/clipboard-apis] Replacing no-break spaces when converting HTML to plain text upon clipboard export (Issue #173)

> The shortest path to have all three do the same thing would be for Gecko to change only not to replace no-break spaces when exporting plain text as plain text.

This was OK.

> Would it be bad in practice (as opposed to principle of deviating from the current interop state) to replace no-break space with regular spaces in HTML to plain text conversion only when the contentEditable-like pattern of alternating spaces and no-break spaces is detected?

This turned out not to be Web-compatible due there being sites that, instead of using the `pre` element or a relevant CSS property, replaced spaces in code examples with no-break spaces and relied on browser reversing the replacement upon copy to clipboard.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/clipboard-apis/issues/173#issuecomment-1420351722
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/clipboard-apis/issues/173/1420351722@github.com>