Search first

• I searched and no similar issues were found

What Happened?

After updating logseq today to this revision 0.9.16 ( e043a2c ) on Windows 10 client, the "restore down" button (opposite of 'maximize') does not work. It shrinks the window momentarily and flashes back to 'maximized' mode. This is happening consistently on two different instances, one without any plugins and hardly used at all.

I checked the dev mode inspector and it is not generating new console messages. This does not seem related to the F11 full screen mode.

Workaround: dragging the windows native title bar area down from the top of the screen does put it into 'restore down' window mode but if that title bar touches the sides of the screen, etc, it will snap back to maximized. (by the look of the buttons the OS considers the page to be currently maximized.)

Rollback OK: seems like running the installer for 0.9.15 gets rid of the problem without further ado. Data seems ok.

Reproduce the Bug

1. maximize logseq 0.9.16 on Windows 10
2. attempt to 'restore down' (e.g. un-maximize it) using the OS button that looks like two stacked windows, next to minimize and the X.

Expected Behavior

I would expect the window to un-maximize as usual.

Screenshots

No response

Desktop or Mobile Platform Information

Windows 10, logseq v .9.16

Additional Context

to my knowledge no funny windowing stuff installed, also I didn't have this issue on the last version.

It makes no difference whether "native title bar" is enabled.

I tried "clearing cache" to no effect.

the Windows "minimize" button function is still working as normal.

• no close and minimize button #5477 seems vaguely similar but was resolved
• Can't move window on macOS #8783 I tried opening the plugins window to break this pattern as that works for some on MacOS semi similar bug, but no effect in windows
• Enhance (UX): Electron loading #10049 maybe this is the patch that caused the bug or related to it?? it was 3 weeks ago and mentions maximized windows.

Are you willing to submit a PR? If you know how to fix the bug.

• I'm willing to submit a PR (Thank you!)