Re: [editing] ContentEditable with UserSelect=None needs to be documented (#20)

@johanneswilm sorry it looks like if I mislead you, but I didn't mean to indicate my preference of how caret movements should be defined. Allow me to go back there if you're ok.

IIUC, we have 3 choices:

1. UA implements all caret movements.
2. Caret movements are turned into intentions:
  1. JS can override them, but UA has default behaviors.
  2. No default behavior defined, JS handles them all.

I'm fine with any of these options. I just wanted to tell you that, if we were going to 1. or 2.i., I wish the spec clarifies what UA should implement clearly. But how much the spec should define and how much it should leave UA to decide would be a tough discussion; platform behaviors and good i18n support are two primary concerns, and doing them correctly is likely to be a hard work. It's still possible, but I suppose you'll find a lot of work in front of you, from studying needs and constraints to coordinating the discussion to a consensus among all editor devs and all UA devs.

If you're happy with the work, I'm fine with any of these options at this moment.

I agree that the caret movements, selections, and focus are tightly coupled. I'm fine where they're defined, but I wish all of them to move forward together. Without all such specs making progress and being stabilized, it's not easy to review and possibly consider implementations.

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