Re: [w3c/editing] Should contenteditable=plaintext-only be standardized? (#162)

@johanneswilm Thank you for the detail explanation! That is what I was afraid of, to aim for something that will be hard to finish for me alone, taking into account my intermediate coding skills. But what I am trying to code is quite simple, that's the reason I though I could use the contenteditable. It's a simple app as a strategic design tool. I want to be able to write sentences in a table cells. All the sentences from cells then gets mirrored and joined to a narrative story below with <span>s. And I want to be able to edit text in both places. Also later I want to add drag and drop functionality to reorder sentences if needed.

So far it works quite well, but the problem was the copy/paste(able) rich text. Which I fixed with plaintext-only for now (but yeah, it has a super limited support). I will have to try your described method. Also, another problem is, if I edit a sentence and delete all of it, the cursor jumps to top above all other sentences. I will have to do something with that, give a min-width somehow... But I need to keep it as an inline element.

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