Re: [Editing] Splitting Selection API Into a Separate Specification

Looking into selection in this brave new world (Shadow DOM for sure, but
there are issues as well with flexbox if I'm not mistaken), is definitely
something we are interested in.

We haven't gotten around it yet which I believe explain our lack of
feedback so far.


2014-03-14 8:43 GMT+09:00 Ryosuke Niwa <rniwa@apple.com>:

> Hi,
>
> It appears that there is a lot of new features such as CSS regions and
> shadow DOM that have significant implications on selection API, and we
> really need a spec. for selection API these specifications can refer to.
>
> Thankfully, Aryeh has done a great work writing the spec. for selection
> API as a part of HTML Editing APIs specification [1] but no browser vendor
> has been able to give meaningful feedback or has implemented the spec due
> to the inherent complexity in HTML editing.  As a result, the specification
> hasn't made much progress towards reaching Last Call or CR.
>
> Given the situation, I think it's valuable to extract the parts of the
> spec that defines selection API into its own specification and move it
> forward in the standards process so that we can make it more interoperable
> between browsers, and let CSS regions, shadow DOM, and other specifications
> refer to the specification.
>
> Any thoughts and opinions?
>
> [1] https://dvcs.w3.org/hg/editing/raw-file/tip/editing.html
>
> - R. Niwa
>
>
>