- From: Jonas Sicking <jonas@sicking.cc>
- Date: Sun, 10 Jan 2016 23:11:15 -0800
- To: Ryosuke Niwa <rniwa@apple.com>
- Cc: Olli Pettay <olli@pettay.fi>, public-webapps WG <public-webapps@w3.org>, public-editing-tf <public-editing-tf@w3.org>
On Sat, Jan 9, 2016 at 6:55 PM, Ryosuke Niwa <rniwa@apple.com> wrote: > >> On Jan 9, 2016, at 6:25 PM, Olli Pettay <olli@pettay.fi> wrote: >> >> Hard to judge this proposal before seeing an API using StaticRange objects. >> >> One thing though, if apps were to create an undo stack of their own, they could easily have their own Range-like API implemented in JS. So if that is the only use case, probably not worth to add anything to make the platform more complicated. Especially since StaticRange API might be good for some script library, but not for some other. > > The idea is to return this new StaticRange object in `InputEvent` interface's `targetRanges` IDL attribute, and let Web apps hold onto them without incurring the cost of constant updates. Could you simply return a dictionary with the parent nodes and parent indexes? / Jonas
Received on Monday, 11 January 2016 07:12:14 UTC