Refactor Selection#scrollIntoView() #3717
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
luin
force-pushed
the
zh-demo-selection
branch
2 times, most recently
from
2ea6fdc to
b108687
Compare
luin
changed the title
luin
force-pushed
the
zh-demo-selection
branch
from
b108687 to
cfbd167
Compare
luin
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Breaking Change: This PR moves scrollIntoView from selection to quill to make it easier to be overridden. The only reasonOn second thought I think semantically it makes sense to keep it in the selection module.scrollIntoViewwas in selection seems to be the usage oflastRangebut in quill we already usethis.selection.lastRange.Also not sure why
if (first == null || last == null) return;is needed so this PR removes it.