Input issues with NXTPAPER 14 tablet

[latot]

Is there an existing issue for this?

• I have searched the existing issues

OS/Web Information

• Web Browser: Chrome 134.0.6998.95
• Local OS: Gentoo 64
• Remote OS: Android 14; 9491G Build/UP1A.231005.007
• Remote Architecture: ARM
• code-server --version: 4.90.3 26c7634 with Code 1.90.2

Steps to Reproduce

1. Open the browser
2. Open any project and wait for a blue button like the Trust workplace
3. Try to click it

Expected

To do the click

Actual

Nothing

Logs

Screenshot/Video

Does this bug reproduce in native VS Code?

No, this works as expected in native VS Code

Does this bug reproduce in GitHub Codespaces?

I did not test GitHub Codespaces

Are you accessing code-server over a secure context?

• I am using a secure context.

Notes

Testing on a Tablet NXTPAPER 14, I'm HTTPS or something but working locally.

[code-asher]

We may need to test Codespaces, I am not sure what we could be doing differently to break this. I have not been able to reproduce unfortunately.

The notification in the screenshot indicates you are using http, I doubt that would cause click issues, but any idea if it reproduces with https?

Seems likely to be related to the device you are on, but not sure what. If you reproduce in Codespaces you can report it directly to Microsoft and they might have a better idea.

[code-asher]

Renaming this a bit to cover the various tablet issues.

[latot]

mm, when I tested this, I needed a usb-c hub, where I connected a mouse and keyboard.

Without a mouse this does not happens, did you try it like that?

[code-asher]

Oops, I did not mean to imply I tested it on a tablet. I just meant I could not reproduce on my machine, so it was likely to be an issue specific to the tablet in some way. Unfortunately I have no tablet to test it on myself.

There have been a few reports about input issues on various mobile and tablet devices, not sure if the causes are the same thing, or if this is something entirely new. All we do is wrap VS Code and I do not believe we are patching any of the input code, so most likely it is a problem with VS Code itself.

[latot]

can we use or test CodeSpaces without $$$ for the test?

[code-asher]

I believe anyone can use Codespaces for free, up to a certain amount of compute.