Skip to content
This repository has been archived by the owner on Sep 6, 2021. It is now read-only.

Add origin parameter to setSelection()/setSelections() #7196

Merged
merged 2 commits into from
Mar 19, 2014

Conversation

njx
Copy link
Contributor

@njx njx commented Mar 13, 2014

@peterflynn - try this and see if setting an origin in your selection code in everyscrub now merges properly again without having to wrap it in an operation with the replaceRange.

Addresses #7182.

@njx
Copy link
Contributor Author

njx commented Mar 14, 2014

Removing "review only" tag - I think we should go ahead and merge this even though it doesn't fix #7182, since it exposes CM functionality that's analogous to the functionality we already expose in Document.replaceRange().

@peterflynn
Copy link
Member

@njx Yep, this fixes it for everyscrub

@njx
Copy link
Contributor Author

njx commented Mar 15, 2014

Oh really? You didn't need to wrap it in an operation?

@njx
Copy link
Contributor Author

njx commented Mar 16, 2014

Ah - apparently it was working for * origins but not + origins (which is what I had tested). Marijn has fixed that in a later patch.

@njx
Copy link
Contributor Author

njx commented Mar 17, 2014

FYI, the fix to this for + origins has also landed.

@njx
Copy link
Contributor Author

njx commented Mar 17, 2014

@redmunds - could you review this one?

@peterflynn
Copy link
Member

Ah, yeah -- everyscrub uses *. And yes, it worked without needing to wrap it in a batch.

@peterflynn peterflynn added this to the Release #38 milestone Mar 17, 2014
@redmunds
Copy link
Contributor

Looks good. Merging.

redmunds added a commit that referenced this pull request Mar 19, 2014
Add origin parameter to setSelection()/setSelections()
@redmunds redmunds merged commit 7d34cf7 into master Mar 19, 2014
@redmunds redmunds deleted the nj/selection-origin branch March 19, 2014 00:36
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants