Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cursor flickering when hovering on the border of frameless window #386

Closed
idlist opened this issue May 7, 2022 · 1 comment
Closed

Cursor flickering when hovering on the border of frameless window #386

idlist opened this issue May 7, 2022 · 1 comment

Comments

@idlist
Copy link

idlist commented May 7, 2022

Firstly mentioned in tauri#3040 and also in #376.

That is to say, when hover the cursor inside the dragging room of resizing operation on the border of a frameless window, the cursor would quickly flicker between "default" and "two-sided arrow", and making it somewhat hard to identify if I can resize the window with current cursor position (since sometimes the cursor would be "default" when I stop moving it inside the dragging room). This behavior is more obvious on screen with high DPI scaling factor.

This GIF shows the flickering when moving the cursor outside of the window (the window is on the left of the CSS border line). The behavior could be also observed when moving cursor into the window.
flickering1

This GIF shows the possible confusion brought by the issue. In this case, the cursor shows "default" inside the dragging room instead of "two-sided arrows", and when I click on the position (yellow circle indicates when I click) I can actually drag the border but I may treat it as I cannot.
flickering2

@amrbashir
Copy link
Member

Closing as I don't think there is much we can do to fix this. We are achieving the resizability for undecorated windows by responding to the win32 window message WM_NCHITTEST on tao and emulating it in wry by synthesizing the same win32 window message in reaction to mousedown and mousemove JS events

@amrbashir amrbashir closed this as not planned Won't fix, can't repro, duplicate, stale Jan 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants