Maximized application in HTML5 has mouse offset

[totaam]

Issue migrated from trac ticket # 2444

component: html5 | priority: major | resolution: fixed

2019-10-14 16:58:00: ffeldhaus created the issue

---

When a window inside an HTML5 client is scaled to the maximum width (e.g. by maximizing the window), the mouse cursor is offset. If the width is modified several times, the offset changes and can increase even more.

This was discovered using XPRA 3.0 and different clients running Linux and Mac OS X with low and high resolutions.

The closed ticket #2124 describes a similar situation.

[totaam]

2019-10-14 17:22:03: ffeldhaus changed component from android to html5

[totaam]

2019-10-15 15:37:59: antoine changed owner from antoine to ffeldhaus

[totaam]

2019-10-15 15:37:59: antoine commented

---

What server OS are you using?
What application can I use to reproduce? What browser?

I have tried with a Fedora server and xterm with a client running in Firefox, there is no offset no matter how many times I maximize or resize.

[totaam]

2019-10-16 15:45:51: ffeldhaus commented

---

I tried this on Mac OS X 10.14.6 with Firefox 69 and Chrome 77 as well as on a Pixelbook with Chrome OS 77.

While the issue immediately occured on my 5K monitor and on the Pixelbook with a resolution of 1200x800, on my MacBook Retina display it only showed up after I resized the Browser. It always occured when I resized the Browser window to half the height. Modifying the width didn't cause problems until very small window sizes.

You can try this for yourself by using my docker image from here:
https://github.com/ffeldhaus/docker-wireshark

Basically you have to install Docker, then run

docker run -p 14500:14500 --name wireshark ffeldhaus/wireshark

and access via

https://<yourhostname>:14500/?username=wireshark?password=wireshark

[totaam]

2019-10-22 09:30:56: antoine changed status from new to assigned

[totaam]

2019-10-22 09:30:56: antoine changed owner from ffeldhaus to antoine

[totaam]

2019-10-22 09:30:56: antoine commented

---

I can't reproduce this with my 4K monitors and wireshark...
So this may take a while to fix.

[totaam]

2020-05-08 15:41:19: antoine commented

---

Simple steps with an xterm or something simple would help me to reproduce it.
Anything that requires a 5K monitor or running a docker container is a non-starter.

[totaam]

2020-10-22 07:51:46: ffeldhaus changed status from assigned to closed

[totaam]

2020-10-22 07:51:46: ffeldhaus set resolution to fixed

[totaam]

2020-10-22 07:51:46: ffeldhaus commented

---

I recently checked this issue with the latest XPRA release (4.0.4) and my 5K monitor (the same where the issue first occured) and I wasn't able to reproduce the issue. Therefore I will close the issue now.