feat: add prop enableSelectionOp and onDOMSelectionChangeThrottleTime #5772
+49
−17
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.
Description
the issue of the anchor, it was discovered that the function for setting the anchor was filtered out during
throttle
. Currently, the default value for this is 100 milliseconds. If it is changed to 0 milliseconds, this problem can be solved.As for the issue of selection, it can be considered to add a
new type
in the operation nameenableSelectionOp
. This type can be used to determine whether the selection of the collaborator needs to be applied to the co-collaborator.This pull request mainly adds the passing of two parameters to solve this issue if developer want to resolve the problem like me. and It will not interfere with the original logic.
Finally, the achieved effect is as follows. It can be seen that both the selection and the anchor are as expected.
Issue
fix #5771
Example
after.mp4