Unable to move the Trilium client window in Windows 11

[Disentimes]

As the title suggest , I have lately been unable to move the trilium "window" lately, from one screen to another or even to a corner in the same screen. I can change its size , minimize it , but it won't move an inch, this is pretty annoying especially if I work on any given projects. I'm on the latest version on Windows 11. Is it a new bug or is there some trick in the "options" I am unaware of?

[dosubot[bot]]

Hi @Disentimes! I'm Dosu and I’m helping the Trilium team.

This is a known issue when using Trilium with the legacy theme and vertical layout on Windows: the window can't be moved because there's no draggable area at the top. This happens because Trilium disables the native title bar and relies on a custom draggable region, which is missing in this layout and theme combination. You can work around this by enabling the native title bar in Options → Appearance → Native Title Bar, or by switching to the horizontal layout or default theme, which restores window movement. If you prefer the custom title bar and vertical layout, you can add custom CSS to create a draggable area, but this requires some familiarity with CSS. Disabling hardware acceleration can fix some UI issues, but it likely won't resolve this specific problem.
More details: see discussion and explanation.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

   

[Disentimes]

I just found out about the native tile bare in Options/Appearance/Native Tiltle Bar just after writing this post (typical).

I'll look into switching to the "horizontal layout/default theme" , the native title bar works, but it looks a bit windows-app-in-1995. Thank you for your swift answer, I guess this thread can be closed.

[eliandoran]

@Disentimes , what theme are you using? The Trilium theme should work without issue.

[Disentimes]

Steelblue , I really like the design , colour and sharpness of this theme.

[eliandoran]

Probably will be fixed alongside with #8402.