- From: Ryosuke Niwa <notifications@github.com>
- Date: Wed, 27 May 2015 19:28:45 -0700
- To: w3c/editing-explainer <editing-explainer@noreply.github.com>
Received on Thursday, 28 May 2015 02:29:18 UTC
I don't think we should be discussing how to design a new API without having a list of concre use cases and problems we're solving. Without that, we wouldn't know the criteria by which each proposal is evaluated. When you say "[the app] cannot really trust the browser in move the caret where the app needs it", what kind of an app are we talking about? e.g. presentation app, spreadsheet app, etc... And exactly in which scenario does the browser not handle caret movement correctly? e.g. when a caret moves across an image in a word processing app. --- Reply to this email directly or view it on GitHub: https://github.com/w3c/editing-explainer/issues/56#issuecomment-106150690
Received on Thursday, 28 May 2015 02:29:18 UTC