Re: [editing-explainer] How does cE=typing support IME text replacement? (#34)

> If we're going with a place holder element route, we could make author scripts place the placeholder at the right place instead of UA automatically inserting it.

That goes against Koji's idea that IMEs should work without developer involvement. IMEs would only work if devs take the time to add that logic to their editor's code. And it sounds like it's not going to be trivial.

Personally I'm not thrilled about using custom elements as a requirement to using cE=typing. Custom Elements is a new technology, and judging by the number of emails that come through my inbox it sounds like there is a lot of work still going on. It seems that if cE=typing becomes dependent on custom elements we inherit a whole lot of uncertainty.

Can we backtrack a bit? contenteditable=true has support for IMEs baked in, with no involvement from the editor devs. If we allow cE=typing to alter the contents of text nodes when an IME is used, wouldn't that be 80% of the solution? cE=typing can already alter contents of a text node during traditional keyboard typing. Is this really that different?

What are the issues that are causing us to want to reinvent the way we handle IMEs?

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/editing-explainer/issues/34#issuecomment-70381032