Text selection boundary accumulates extra space after repeated pasting
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 52/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- typescript
- Domain
- frontend
Research direction
Reproduce the issue with a text node on the canvas by repeatedly copying and pasting its contents in edit mode. Trace the text width calculation and the selection boundary update, then verify that the left and right gaps remain equal after repeated pastes in Chrome.
Written by the indexing model from the issue text.
Description
Description
When content is pasted repeatedly into a text node, the gap between the right edge of the text selection boundary and the actual end of the text keeps increasing. This appears to be caused by an incorrect text width calculation.
Steps to reproduce
- Drag a text node onto the canvas.
- Double-click the text node to enter edit mode.
- Select all of the current text and copy it.
- Place the cursor at the end of the current text.
- Paste the copied content repeatedly.
- Observe the distance between the right edge of the text selection boundary and the actual end of the text.
Actual behavior
The empty space between the right edge of the text selection boundary and the actual end of the text increases with each paste.
Expected behavior
The distance between the right edge of the selection boundary and the end of the text should remain constant. It should match the distance between the left edge of the selection boundary and the beginning of the text, regardless of how many times content is pasted.
Environment
- OS: macOS
- Browser: Chrome
- Dominant language
- TypeScript
- Stars
- 703
- Forks
- 61
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from worktile/plait
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
area: tooling tracking
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
area: mind design enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
area: table design enhancement
Difficulty 5/5 Over a week Newbie friendliness 28/100
-
documentation tracking
Difficulty 5/5 Over a week Newbie friendliness 25/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
milind-soni/OpenMausBot#6730 ·
Maintainers usually reply within 1 day
-
`@angular/[email protected]` depends on vulnerable Vite 7.3.7 - GHSA-p4f5-76q4-ffq7 (Critical RCE)Openarea: @angular/build
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
angular/angular-cli#34764 ·
Maintainers usually reply within 1 day
-
status/need-triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
google-gemini/gemini-cli#30384 · 1 comment ·
Maintainers usually reply within 1 day
-
P2
Difficulty 1/5 Under an hour Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
area:image documentation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day