Floating sidebar is not kept open when cursor at the left-most position

[angrybacon]

Captchas

• I have read the instructions.
• I have searched existing issues and avoided creating duplicates.
• I am not filing an enhancement request.
• I have checked that this issue cannot be reproduced on Mozilla Firefox.
• I have checked that this issue can be reproduced once I removed all my Mods and Custom CSS.

What happened?

• Double click the title bar in order to ensure the Zen window is correctly maximized
• Toggle compact mode on
• Move cursor the extreme left of the display (single macOS laptop in my case)
• The floating sidebar correctly shows
• The floating sidebar disappears after the usual delay

I'd expect the floating sidebar to remain open. Note also in the screencast how moving the cursor back towards the center of the display enters the hover area again and toggle the floating sidebar again

Floating.Sidebar.Issue.4971.mov

There seem to be a small area where the cursor can be outside of Zen even though it is maximized, I'd expect the hover zone that reveals the floating sidebar to account for that.

Version

1.10.3b 1.11.2b

What platform are you seeing the problem on?

macOS - aarch64

What component is this issue related to?

Compact Mode

Relevant log output if applicable

[angrybacon]

Copied from #4971

[Propheticus]

Still valid in 1.11.2b?
I cannot reproduce on Windows.

[angrybacon]

I've reported it as a macOS issue, I haven't tested on Windows and I don't have the same "maximized" setup on Arch so I can't try to reproduce there either

Edit: this was closed by mistake, and I can't reopen it myself apparently I can now

[Propheticus]

I've reported it as a macOS issue, I haven't tested on Windows and I don't have the same "maximized" setup on Arch so I can't try to reproduce there either

Edit: this was closed by mistake, and I can't reopen it myself apparently I can now

That's not what I meant. I meant can you retest on Mac since my retest on Windows is not a guarantee it's also fixed for you.
( You reported on 1.10.3b and 1.11.2b was just released, I don't see the issue so thought it worth a double-check)

[angrybacon]

Oh ok, good call thanks for clarifying. I just reproduced on 1.11.2b. I'll add that version to the original post