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

On 3/13/14 7:43 PM, ext Ryosuke Niwa wrote:
> 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?

When we last discussed this spec vis--vis the Editing CG and WebApps 
[1], the CG's position was the spec was not ready for "Recommendation 
track work". As such, I would like to hear from Aryeh and/or the Editing 
CG re Ryosuke's proposal.

One factor to consider re WebApps formally working on this spec is 
whether there we have sufficient resource commitment(s) re editing, 
testing, etc. Do we have such commitment(s)?

-Thanks, AB

[1] 
<http://lists.w3.org/Archives/Public/public-webapps/2011JulSep/1617.html>

>
> [1] https://dvcs.w3.org/hg/editing/raw-file/tip/editing.html
>
> - R. Niwa
>
>

Received on Friday, 14 March 2014 12:59:00 UTC