Re: [w3c/selection-api] Fix selection.modify() to use resolved text direction instead of inline base direction (PR #357)

@dandclark commented on this pull request.



> @@ -731,6 +731,15 @@ <h2>
             selection by <var>granularity</var>.
             </li>
           </ol>
+          <p>
+            The <dfn>resolved text direction</dfn> at a <a>boundary point</a>
+            is <a data-xref-type="css-value"
+            data-xref-for="direction">ltr</a> if the bidi embedding level of

Thanks, this is easier to understand. I think it could be made clearer still by referring to the [embedding direction](https://www.unicode.org/reports/tr9/tr9-51.html#BD3) only; the detail about embedding levels is probably best left to the Unicode spec.
So this could say something like:
```
The <dfn>resolved text direction</dfn> at a <a>boundary point</a>
is <a data-xref-type="css-value" data-xref-for="direction">ltr</a> if the <a 
href="https://www.unicode.org/reports/tr9/#BD3">embedding direction</a>
([[!UAX9]] BD3) of the character at that position is `L` and
<a data-xref-type="css-value" data-xref-for="direction">rtl </a> if the
<a  href="https://www.unicode.org/reports/tr9/#BD3">embedding direction</a> ([[!UAX9]] BD3)
of the character at that position is `R`.
```

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/selection-api/pull/357#discussion_r3168798199
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/selection-api/pull/357/review/4206135780@github.com>