Meanwhile, contenteditable="plaintext-only" has been in Chromium for seven years, and just landed in Safari 17.0, and I still don’t understand why anyone ever thought it sounded like a good idea, given how contenteditable elements aren’t part of form data so it’s unsuitable in the only places I’ve actually seen people suggest its use (and this does actually matter, you can’t just smooth it over with a little JavaScript: it affects things like the browser’s form memory when you navigate history or restart the browser).<p>(Mind you, contenteditable=plaintext-only <i>does</i> still have one thing going for it: you can have it inline, mid-paragraph with natural wrapping inside it, whereas the closest actual form fields can manage is inline-block, which will break funny.)