Re: [w3c/editing] TPAC 2022 (Issue #400)

@zcorpan No, we wrote this at the time with the objective to create a minimal interface for JS devs to create text editors. We were never going to have all the extra modes, but we couldn't figure out which of them would be more useful, or whether it would be enough to just use the pre-existing plaintext-only. We went in circles several times. Then at some point we thought that we should first finish with the Input Events spec and have that implemented everywhere. And then when Chrome decided not to fully implement Input Events, we were waiting for the replacement - which is only now coming in the form of EditContext.

So I think there are two parts that are of interest when it comes to plaintext-only - first there is documenting how it currently works and potentially implement it in browsers that don't yet have it.

The other part is to continue the work from back then and find out whether or not it can be used when beuilding richtext editors in combination with EditContext and/or Input Events, wehther that would still require another mode, or whether other modes are not really needed at all as one can simply preventDefault all the beforeinput events.

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

Message ID: <w3c/editing/issues/400/1244384553@github.com>