- From: Johannes Wilm <notifications@github.com>
- Date: Wed, 03 Jun 2015 03:44:48 -0700
- To: w3c/editing <editing@noreply.github.com>
- Message-ID: <w3c/editing/issues/58@github.com>
Options mentioned so far: A) Don't move the caret by default and don't define default behavior. B) Move the caret by default and define the default behavior. C) Move the caret by default and define some of the default behavior and leave the rest to be decided by UA/platform (for example: let UA decide on line block direction movement, but define inline movement in spec). D) Move the caret by default, and define all it's default movement in the spec. This is the default inline movement we initially had in the spec before it was removed: <h3>Default caret movement pattern</h3> <section> <h4>Caret movement within <a>CE Typing Node</a></h4> <p>Each key press event in the `inline direction` or in the direction opposite to the `inline directions` triggers the movement of the caret of one position within the current <a>CE Typing Node</a>.</p> </section> <section> <h4>Caret movement at the end of a <a>CE Typing Node</a></h4>If the caret is at the end of a <a>CE Typing Node</a> before the movement takes place, and the requested movement would cause it to go beyond the end of the <a>CE Typing Node</a>, the caret is moved into the start of the next following <a>CE Typing Node</a> that is part of the same <a>CE Typing Container</a>. If this movement did not cause it to move by at least 1px, the caret is moved one additional position. <p></p> <p>If there is no following <a>CE Typing Node</a> to which the caret could be moved, it is not moved.</p> </section> <section> <h4>Caret movement at the start of a <a>CE Typing Node</a></h4>If the caret is at the start of a <a>CE Typing Node</a> before the movement takes place, and the requested movement would cause it to go beyond the start of the <a>CE Typing Node</a>, the caret is moved into the start of the last preceding <a>CE Typing Node</a> that is part of the same <a>CE Typing Container</a>. If this movement did not cause it to move by at least 1px, the caret is moved one additional position. <p>If there is no previous <a>CE Typing Node</a> to which the caret could be moved, it is not moved.</p> </section> --- Reply to this email directly or view it on GitHub: https://github.com/w3c/editing/issues/58
Received on Wednesday, 3 June 2015 10:45:17 UTC