Re: [Selection] Should selection.getRangeAt return a clone or a reference?

2015-01-28 Thread Aryeh Gregor
On Tue, Jan 27, 2015 at 4:49 PM, Koji Ishii wrote: > 3 proposals so far: > > Proposal A: Leave it undefined. If it's not causing interop issues, we > can leave it. > Proposal B: Clone. > Proposal C: Live. I can live with any, but prefer B.

Re: [Selection] Support of Multiple Selection (was: Should selection.getRangeAt return a clone or a reference?)

2015-01-28 Thread Aryeh Gregor
On Tue, Jan 27, 2015 at 4:31 PM, Koji Ishii wrote: > It's true that you could use multi-range selections to select in > visual order. But there are bunch of operations defined against > selections. What does it copy? What will happen when you type "a" to > replace the selected text? Spell check? B