Visible UM.Message makes PickingPass return far off, invalid co-ordinates

[Slashee-the-Cow]

Cura Version

5.0..0-5.10.0

Operating System

Windows 11 / openSUSE Tumbleweed

Printer

Issue with Cura independent of printer.

Reproduction steps

The easiest way to test is using my new(ish) plugin: https://github.com/Slashee-the-Cow/TabAntiWarpingReborn
Download the current commit or the latest release. Install as usual.

1. Load Cura with plugin installed. Add object to the scene, switch to the tool, click on object a few times to add some tabs. Keep an eye on cura.log and to make your life easier filter for "TabAntiWarpingReborn" if you can. It will log the co-ordinates of the object that has been clicked, and the co-ordinates returned by the PickingPass. All should be normal.
2. In the plugin's main folder, open TabAntiWarpingReborn.py in a text editor and uncomment/replace line 159 with Message(text = "You clicked!", title = "Grats!").show()
3. Restart Cura, add object to scene. Switch to the tool and click on the object 2-3 times. The first one should successfully create a tab. Any subsequent ones while the test Message is shown will not be created and show an error saying Cura got the wrong co-ordinates (or very rarely, will appear somewhere else on the build plate.
4. Check cura.log. You'll see the first tab was created successfully, but the co-ordinates returned by the subsequent PickingPass operations while the Message was on screen are probably quite far off the build plate in at least one axis. It's also possible for the mouse click to be in different locations (which is why I'm logging the co-ordinates of the Event) but return the same co-ordinates from the PickingPass.
5. In Cura, wait until the Message has disappeared. Click on your object a couple of times again. Again, the first one will be successful but any subsequent ones will return far off co-ordinates.

Actual results

Without the Message enabled in the code, all clicks will log valid co-ordinates returned by the PickingPass and create a tab.

With the Message enabled in the code, the first click will log valid co-ordinates and create the tab. Subsequent clicks while Message is still visible will log that the object being clicked is still in the same location, but that the PickingPass is returning co-ordinates well outside the build plate, at which point a function in the plugin kicks in and stops it creating a tab outside the build plate.

Wait until all Messages hide and the behaviour will repeat that cycle.

Expected results

Regardless of the presence of a UM.Message on screen, the PickingPass should log the correct co-ordinates and a support tab created where intended every click.

Add your .zip and screenshots here ⬇️

Behaviour is the same in 5.0, 5.6, 5.9 and 5.10 (I don't have time to test all of them). Tested in both Windows and Linux at multiple resolutions and window sizes. All exhibit the same behaviour.