Text Box Bounding Box Glitch and Freezing in Google Chrome with Google Drive Integration

[JC-808]

• 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:

1. Open draw.io in Google Chrome with a file saved in Google Drive.
2. Select or create a text box.
3. Modify the text box using the mouse.
4. Observe the size indicator freezing in place.
5. 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

[draw-io-triage-bot]

👋 Thank you for opening this issue!

---

Summary: The user reports a visual glitch where the text box bounding box / size indicator freezes in place during mouse-based modifications in draw.io on Chrome with Google Drive storage, requiring a page reload to clear.

---

📝 Additional Information Needed

To help us investigate this more effectively, could you please provide:

• draw.io version: The specific version of draw.io being used (visible in Help > About or the page footer) is not provided.
• Chrome version: The specific version of Google Chrome being used is not mentioned.
• Reproducibility with other storage backends: It's unclear whether this issue is specific to Google Drive integration or also occurs with local storage, OneDrive, etc.
• Reproducibility in other browsers: It would help to know if this issue also occurs in Firefox, Edge, or other browsers, to narrow down whether it's Chrome-specific.
• Hardware acceleration: Whether Chrome's hardware acceleration is enabled or disabled, as rendering glitches like this can sometimes be related to GPU compositing issues.

We also have some questions:

• Can you provide the draw.io version you are using (found in Help > About)?
• What version of Google Chrome are you running?
• Does this issue also occur when using draw.io with local storage (i.e., not Google Drive), or is it specific to the Google Drive integration?
• Does this issue reproduce in other browsers such as Firefox or Edge?
• Have you tried disabling hardware acceleration in Chrome (Settings > System > Use hardware acceleration when available) to see if the rendering glitch persists?
• Does this happen with a new blank diagram, or only with a specific existing file? If specific, could you share a minimal .drawio file that reproduces the issue?

📋 Bug Report Template

**Environment:**
- draw.io version: [e.g., web app / desktop 24.x.x / Confluence plugin]
- Browser (if web): [e.g., Chrome 120, Firefox 121]
- OS: [e.g., Windows 11, macOS 14, Ubuntu 22.04]

**Steps to Reproduce:**
1. Go to ...
2. Click on ...
3. See error

**Expected Behavior:**
What you expected to happen.

**Actual Behavior:**
What actually happened.

**Screenshots/Files:**
If applicable, add screenshots or attach the .drawio file.

---

---

_{🤖 This is an automated response to help with initial triage. A human maintainer will review this issue. If you've provided all the requested information, no further action is needed - we'll get back to you soon!}

[JC-808]

Environment:

draw.io version: 31.1.9

Browser (if web): Chrome 151.0.7922.109

OS: Windows 10

Steps to Reproduce:

Open draw.io (tested with both a blank diagram and an existing file).

Create or select a text box without a shape.

Edit its size or text content.

Resize the text box and observe the leftover artifact/visual glitch remaining on the screen.

Expected Behavior:
UI elements or selection/resize markers should only appear while actively modifying the element and disappear once the action is complete.

Actual Behavior:
The visual residue or editing artifact remains stuck on the screen after changing the size of the text box.