Re: [w3c/editing] Behavior of insert* commands for contenteditable=plaintext-only (Issue #419)

yisibl left a comment (w3c/editing#419)

I've noticed that Chrome and Firefox behave differently with carriage returns; Firefox inserts `<br>`, while Chrome does not.

Imagine if this feature is used in code highlighting scenarios, where users usually don't want the extra `<br>`.

![Image](https://github.com/user-attachments/assets/4cd6bbbc-f58f-4628-9252-1eae5e5a38e3)

This would seriously affect interoperability, and I think it's something that needs to be standardized in the specification as soon as possible.

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

Message ID: <w3c/editing/issues/419/2822998199@github.com>