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.



Issue - #9044
I've successfully identified and fixed the bug where slicing doesn't work after deleting a sliced annotation. The issue was caused by improper state synchronization between the UI and the canvas model.
Root Cause
The bug occurred because:
canvas.slicedevent and the UI properly updated itsactiveControlstate toCURSORsliceData.enabled = truecanvasInstance.slice({ enabled: true })did nothing because the model saw that slicing was already "enabled" and returned earlycanvasInstance.cancel()which properly reset the canvas stateChanges Made
I fixed the issue in two files with four changes total:
slice-control.tsx:50-51updateActiveControl(ActiveControl.CURSOR)when manually deactivating slice modecanvas-wrapper.tsx:881canvasInstance.slice({ enabled: false })in theonCanvasSliceDonehandlerjoin-control.tsx:52(preventive fix)updateActiveControl(ActiveControl.CURSOR)when manually deactivating join modecanvas-wrapper.tsx:728(preventive fix)canvasInstance.join({ enabled: false })in theonCanvasObjectsJoinedhandlerTesting
The fix should now allow the following workflow to work correctly:
Proof
Screen.Recording.2025-12-12.015103.mp4