so I typed the whole thing out, only to find my cache had been cleaned and that was all lost.) - suffice it to say it seems to be errors about the sandbox and some kind of.
The error logs in the xterm for the launching of chromium-browser are the same whichever client launches (and I still can't manage to sync any copy events from a Fedora server-side xterm to a Windows client-side clipboard-clipboard. 15:33:37,714 process_button_action(Protocol(ws websocket: 192.168.1.81:14500 37 doesn't mean that 24692 >= 24737.Īs long as I had the server running though, I tried more with the launching of chromium-browser from an xterm with python 3.0.3 client vs. Here's a snippet of me scrolling to the left (as in my physical fingers are moving to the left), but the image I'm zoomed in on moves to the right (incorrectly, I verified with local Chrome that it should be moving to the left with my fingers). So I double checked this with my laptop's trackpad (after 4 hours of updates, I'm not even joking) and the horizontal scroll is definitely reversed as of r19581. Oh so it looks like I really have no idea what I'm doing then. Please provide xev button numbers and the server's "-d mouse". This ticket is about scrolling, which is usually done using wheels or touchpad gestures.
I wonder if there's something else going on here - I'll update my laptop which has an Apple trackpad versus my Logitech MX, and see if I can get ahold of an "Official" Apple Mouse. I upped my server from r19572 to r19574 and I see no change.
Please confirm that this fixes things so that I can backport. Wed, 17:53:29 GMT - Antoine Martin: owner changed Reversing the buttons again will make it work as expected. Those were working as expected and as such are now reversed in the X-direction. As such, the Wacom tablet X-direction was reversed not the mouse buttons. I got this ticket and #1157 mixed up, so I was testing this with the Wacom Tablet. I made a serious mistake when testing this ticket.
On the mac mini, the left and right horizontal buttons both trigger button 3 (middle click).įri, 11:47:53 GMT - Antoine Martin: milestone set On windows using those button triggers navigation - making it impossible to figure out the button number that javascript should be seeing. So r19073 remaps those buttons to 8 / 9, since that's what xev sees without xpra - I'm not 100% sure that's right though. Those events come up a individual clicks, and they're using the same button number (4 and 5) as what vertical scrolling is meant to use (with r19072 to get javascript console debug logging with "mouse" debug enabled): I only have horizontal buttons, no wheel on any of my test devices. What application did you use to decide what is the desired scroll direction? (both native and through xpra)
Wed, 03:54:22 GMT - Antoine Martin: owner changedĭid you test horizontal scrolling with a non-macos OS to compare? (ideally ms windows) That would bring it in line with local MacOS applications. We need to invert the values on MacOS but only for the horizontal. Not sure if that means that we're doing the right thing or that we need to invert the values on macos. Sat, 03:17:14 GMT - Antoine Martin: owner changed Max Mena to Antoine MartinĬhecked with Firefox and Chrome in OSX - and yes the scroll direction is reversed. Do we need to map the macos scroll direction differently? (ie: is it somehow normalized the "right" way by some browsers)įri, 17:20:27 GMT - J. UInput.wheel_motion(4, 0.5740) REL_WHEEL: works for me, could be interesting for you guys. Max Menaĭone in r18920, the html5 client will now trigger precise scroll events if the server has uinput enabled: Sat, 14:04:24 GMT - Antoine Martin: owner changedĬhanged from Antoine Martin to J.