Re: [Editing] [DOM] Adding static range API

2016-01-10 Thread Jonas Sicking
On Sat, Jan 9, 2016 at 6:55 PM, Ryosuke Niwa wrote: > >> On Jan 9, 2016, at 6:25 PM, Olli Pettay 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,

[Editing] [DOM] Adding static range API

2016-01-09 Thread Ryosuke Niwa
Hi, This is yet another feedback from multiple browser vendors (Apple, Google, Microsoft) that got together in Redmond last Thursday to discuss editing API and related events. For editing APIs, it's desirable to have a variant of Range that is immutable. For example, if apps were to create

Re: [Editing] [DOM] Adding static range API

2016-01-09 Thread Olli Pettay
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

Re: [Editing] [DOM] Adding static range API

2016-01-09 Thread Ryosuke Niwa
> On Jan 9, 2016, at 6:25 PM, Olli Pettay 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