Skip to content

bug/perf: windows - drag renders character through lagged hole (partial occlusion) #1365

Closed

Description

@omesser

Summary

On Windows, while dragging the character there is a visual artifact: the sprite appears rendered through a hole, with a lag between where the character is drawn and where the hole is drawn. Depending on drag speed, the character is partially occluded.

Found during live prove of #1351 tip fd4bebaf (dual-monitor drag). Parent context: #1357 / cross-display drag work.

Observed (DESKTOP, Windows)

  1. Grab/drag the character.
  2. Move at varying speeds (especially quicker drags).
  3. Character looks clipped / drawn through a hole that trails the true sprite position — hole and character positions diverge briefly → partial occlusion.

Expected

During drag, the full character should stay visible and aligned with its hit/clip region — no lagged “hole” occlusion artifact.

Notes

  • #1351 live prove: no white flicker across display bounds — PASS. This is a separate Windows UI rendering bug.
  • May relate to layered window / transparency / region update timing on Windows; needs investigation separate from the flicker Soft-FIX.

Status: Todo

— Cursor agent (Coder), on @omesser's behalf.

Activity

  1. added
    bugSomething isn't working
    windowsRun the Windows compile job on this pull request
    on Oct 6, 2026
  2. added this to the V1 milestone on Oct 6, 2026
  3. omesser commented on Oct 7, 2026

    @omesser
    OwnerAuthor

    This is the same Windows draw bug as #1339: the window region trailing the drawn sprite, so a fast drag cuts the character off.

    #1378 (merged as 9bdff93f) made the region cover where the sprite is actually drawn and closed #1339. Clipping was reported again on Windows on 2026-10-07, and the A/B steps to check it are in this comment on #1378. #1391 has also changed the Windows region code since then.

    I'm leaving this open as the tracker until a live drag on current main shows whether the clipping is gone.

    — Cursor agent (Coder), on @omesser's behalf.

  4. changed the title [-]Windows: drag renders character through lagged hole (partial occlusion)[/-] [+]perf: windows - drag renders character through lagged hole (partial occlusion)[/+] on Oct 13, 2026
  5. changed the title [-]perf: windows - drag renders character through lagged hole (partial occlusion)[/-] [+]fix: windows - drag renders character through lagged hole (partial occlusion)[/+] on Oct 13, 2026
  6. changed the title [-]fix: windows - drag renders character through lagged hole (partial occlusion)[/-] [+]bug/perfh: windows - drag renders character through lagged hole (partial occlusion)[/+] on Oct 13, 2026
  7. changed the title [-]bug/perfh: windows - drag renders character through lagged hole (partial occlusion)[/-] [+]bug/perf: windows - drag renders character through lagged hole (partial occlusion)[/+] on Oct 13, 2026
  8. omesser commented on Oct 16, 2026

    @omesser
    OwnerAuthor

    Live drag on Windows (DESKTOP-UQIE144, main 7171f04f): the Character no longer clips, so the original lagged-hole bug is gone. A smaller clipping of the speech bubble is tracked in #1568.

    — Cursor agent (Coder), on @omesser's behalf.

  9. moved this from Todo to Done in Fidgeton Oct 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingready-for-agentFully specified, ready for an AFK agentwindowsRun the Windows compile job on this pull request

    Projects

    • Status
      Done

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions