Text Box Bounding Box Glitch and Freezing in Google Chrome with Google Drive Integration
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 8.2k
- Forks
- 1.2k
- PR merge metrics
- No merged PRs in 30d
Description
- I agree to follow the Code of Conduct that this project adheres to.
- I have searched the issue tracker for a bug report that matches the one I want to file, without success.
Describe the bug
When modifying a text box using the mouse, the bounding box/size indicator glitches and gets stuck in a fixed position. It only moves to a different location once another modification is made. This happens with every text box, and the only way to clear it is by reloading the page.
To Reproduce
Steps to reproduce the behavior:
- Open draw.io in Google Chrome with a file saved in Google Drive.
- Select or create a text box.
- Modify the text box using the mouse.
- Observe the size indicator freezing in place.
- Make another modification to see it jump to a different location.
Expected behavior
The size indicator and bounding box should follow the mouse interaction smoothly and update/disappear correctly without freezing or requiring a page reload.
Screenshots
(Drag and drop or paste your screenshot here)
[Attach the photo of the error here]
Desktop (please complete the information):
- OS: Windows 10
- Browser: Google Chrome
- Storage: Google Drive
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
No source files or tests are named. Reproduce the text-box mouse modification in Chrome with a file saved to Google Drive, then trace the bounding-box and size-indicator update path; done means the indicator follows the interaction and clears without a page reload.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100