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

[Bug]: Context menu appears in a random location when using the touch screen #43678

Open
3 tasks done
griffinhardy opened this issue Sep 10, 2024 · 3 comments
Open
3 tasks done
Labels

Comments

@griffinhardy
Copy link

griffinhardy commented Sep 10, 2024

Preflight Checklist

Electron Version

32.0.2

What operating system(s) are you using?

Windows

Operating System Version

Windows 11 Pro 23H2

What arch are you using?

x64

Last Known Working Electron version

No response

Expected Behavior

When using the touch screen, if you do a long press to bring up the context menu, the context menu should appear right where you were touching the screen.

Actual Behavior

When using the touch screen, if you do a long press to bring up the context menu, it seem that the context menu appears in a different place each time the window is resized.

Testcase Gist URL

https://gist.github.com/griffinhardy/2f23ff4487e59538ce33953ce65daf8a

Additional Information

The context menu appears in the appropriate spot when you use a mouse and right-click. The context menu when doing a long press on a touch screen device is what is not in the correct place. It is in the same random place every time until the window is resized, and then it is in a new random place until the window is resized.

@georgexu99 georgexu99 added the blocked/need-repro Needs a test case to reproduce the bug label Sep 11, 2024
@electron-issue-triage
Copy link

Hello @griffinhardy. Thanks for reporting this and helping to make Electron better!

Would it be possible for you to make a standalone testcase with only the code necessary to reproduce the issue? For example, Electron Fiddle is a great tool for making small test cases and makes it easy to publish your test case to a gist that Electron maintainers can use.

Stand-alone test cases make fixing issues go more smoothly: it ensure everyone's looking at the same issue, it removes all unnecessary variables from the equation, and it can also provide the basis for automated regression tests.

Now adding the blocked/need-repro Needs a test case to reproduce the bug label for this reason. After you make a test case, please link to it in a followup comment. This issue will be closed in 10 days if the above is not addressed.

@griffinhardy
Copy link
Author

griffinhardy commented Sep 11, 2024

I have updated the ticket description to include a GitHub gist. It is very basic and it just allows a context menu to pop up.

@electron-issue-triage electron-issue-triage bot removed the blocked/need-repro Needs a test case to reproduce the bug label Sep 11, 2024
@mlaurencin
Copy link
Member

@griffinhardy Did you mean to include an menu implementation in your gist? https://www.electronjs.org/docs/latest/api/menu#class-menu
I am unable to reproduce this issue on Windows 11 using my touch screen. Long pressing in the body of the window has nothing appear and long pressing the title bar results in a context menu appear where I press. This does not change whether I move or resize the window.

I’m setting the blocked/need-info label for the above reasons. This issue will be closed 10 days from now if there is no response.

@mlaurencin mlaurencin added the blocked/need-info ❌ Cannot proceed without more information label Oct 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
No open projects
Status: 👍 Does Not Block Stable
Development

No branches or pull requests

3 participants