Mintplex-Labs/anything-llm
1
0
Fork 0
mirror of https://github.com/Mintplex-Labs/anything-llm.git synced 2026-07-19 14:13:35 -04:00
Code Issues 328 Packages Projects Releases 10 Wiki Activity

[GH-ISSUE #5565] [BUG]: Assistant UI border artifact #5169

New Issue
Closed
opened 2026-06-05 14:52:25 -04:00 by yindo · 3 comments
yindo commented 2026-06-05 14:52:25 -04:00
Owner
Copy Link
Copy Source

Originally created by @gurpal2000 on GitHub (May 1, 2026).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/5565

Originally assigned to: @timothycarambat on GitHub.

How are you running AnythingLLM?

AnythingLLM desktop app

What happened?

When the assistant is invoked the border of the application is showing unwanted artifacts.

There's an extra 1px (?) black line that follows the left hand edge.

Image

Are there known steps to reproduce?

Open up the assistant at resolution 1920x1080 at 125% scaling.
Windows 11. Dell Latitude 5491.

Possibly something to do with resolution / HiDPI ?

LLM Provider & Model (if applicable)

N/A

Embedder Provider & Model (if applicable)

N/A

Originally created by @gurpal2000 on GitHub (May 1, 2026). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/5565 Originally assigned to: @timothycarambat on GitHub. ### How are you running AnythingLLM? AnythingLLM desktop app ### What happened? When the assistant is invoked the border of the application is showing unwanted artifacts. There's an extra 1px (?) black line that follows the left hand edge. <img width="197" height="303" alt="Image" src="https://github.com/user-attachments/assets/26eeef17-d373-44eb-9f2b-513cc1e6aa5b" /> ### Are there known steps to reproduce? Open up the assistant at resolution 1920x1080 at 125% scaling. Windows 11. Dell Latitude 5491. Possibly something to do with resolution / HiDPI ? ### LLM Provider & Model (if applicable) N/A ### Embedder Provider & Model (if applicable) N/A
yindo added the bugUI/UXDesktopOS: Windows labels 2026-06-05 14:52:25 -04:00
yindo closed this issue 2026-06-05 14:52:26 -04:00
yindo commented 2026-06-05 14:52:26 -04:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (May 1, 2026):

Interesting, will see if I can repro on mine. I have the exact same machine at home

<!-- gh-comment-id:4361929873 --> @timothycarambat commented on GitHub (May 1, 2026): Interesting, will see if I can repro on mine. I have the exact same machine at home
yindo commented 2026-06-05 14:52:26 -04:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (May 21, 2026):

This is a known Electron/Windows DWM compositor issue with transparent: true on frameless windows at fractional display scaling - from what I can tell, this is only occurring on scaling that do not end in 0 but that may be resolution specific.

When Electron creates a transparent frameless window on Windows, it uses a legacy DWM composition hack. At non-integer scale factors (e.g., 1.25x), the DWM's frame bounds don't perfectly align pixel-for-pixel with the rendered content due to sub-pixel rounding. This manifests as a 1px black line along the window edge — the window's own compositor frame "bleeding through" where the transparency layer has a rounding mismatch.

This does not occur on macOS (which uses a completely different compositing model) or at 100%/200% scaling on Windows (integer scale factors don't have the rounding issue).

Closing this, but the issue is mirrored to the desktop wrapper repo and will be solved there. In the meantime, you can increase scaling to like 150 and it would go away but obviously that might not be what you want. For now, until we migrate to backgroundMaterial for windows - this is an annoying UI detail

<!-- gh-comment-id:4508555556 --> @timothycarambat commented on GitHub (May 21, 2026): This is a known Electron/Windows DWM compositor issue with `transparent: true` on frameless windows at **fractional display scaling** - from what I can tell, this is only occurring on scaling that do not end in `0` but that may be resolution specific. When Electron creates a transparent frameless window on Windows, it uses a legacy DWM composition hack. At non-integer scale factors (e.g., 1.25x), the DWM's frame bounds don't perfectly align pixel-for-pixel with the rendered content due to sub-pixel rounding. This manifests as a 1px black line along the window edge — the window's own compositor frame "bleeding through" where the transparency layer has a rounding mismatch. This does **not** occur on macOS (which uses a completely different compositing model) or at 100%/200% scaling on Windows (integer scale factors don't have the rounding issue). Closing this, but the issue is mirrored to the desktop wrapper repo and will be solved there. In the meantime, you can increase scaling to like 150 and it would go away but obviously that might not be what you want. For now, until we migrate to `backgroundMaterial` for windows - this is an annoying UI detail
yindo commented 2026-06-05 14:52:26 -04:00
Author
Owner
Copy Link
Copy Source

@gurpal2000 commented on GitHub (May 21, 2026):

Very good, and thank you for the detailed explanation.

<!-- gh-comment-id:4508639332 --> @gurpal2000 commented on GitHub (May 21, 2026): Very good, and thank you for the detailed explanation.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Desktop
Docker
Integration Request
Integration Request
OS: Linux
OS: Mobile
OS: Windows
UI/UX
blocked
bug
bug
core-team-only
documentation
duplicate
embed-widget
enhancement
feature request
github_actions
good first issue
investigating
needs info / can't replicate
possible bug
pull-request
Mirrored from GitHub Pull Request
 question
stage: specifications
wontfix
No Label Desktop OS: Windows UI/UX bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Mintplex-Labs/anything-llm#5169
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?