- From: Johannes Wilm <notifications@github.com>
- Date: Mon, 17 Aug 2015 03:21:12 -0700
- To: w3c/editing <editing@noreply.github.com>
Received on Monday, 17 August 2015 10:21:39 UTC
I think we need to depend on the selection API being in place. I can see it being attractive to replicate everything we need here, just to make sure that it's there when we need it, but currently it seems that the Selection API is more on track to getting into browsers than this spec. Also notice that this is supposed to be a first module, and later modules should then be able to remove large pieces of JavaScript polyfills. This is only supposed to be functional, not represent the ideal division of labor between browsers and JS editors. But maybe we can add some examples into the spec about how certain operations are done, and in those link to the Selection API spec, just to make sure that UA developers get the point. --- Reply to this email directly or view it on GitHub: https://github.com/w3c/editing/issues/71#issuecomment-131767914
Received on Monday, 17 August 2015 10:21:39 UTC