ARC++: touch event position is wrong in full screen
Reported by
luxte...@gmail.com,
Oct 11 2016
|
|||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; CrOS x86_64 8530.80.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.100 Safari/537.36 Steps to reproduce the problem: 1. install djay 2 free from google play 2. try to click any buttons in bottom of screen 3. I have to click much lower pixel than actual button position. What is the expected behavior? What went wrong? see mouse pointer's position in the attached picture. I want to click 'automix' button. I have to click this wrong position. Did this work before? N/A Chrome version: 53.0.2785.100 Channel: n/a OS Version: 8530.80.0 Flash Version: Shockwave Flash 22.0 r0
,
Oct 11 2016
,
Oct 11 2016
,
Oct 11 2016
,
Nov 28 2016
Hi, Which device is this and is this on the internal display or external display? I suspect from the offset that the app is getting the wrong coordinates and using the wrong API and offset by the window decoration.
,
Nov 28 2016
I see this on various android apps on an Acer R11. Version 55.0.2883.54 beta (64-bit) No specific apps, it comes and goes, but it happens the most in fullscreen. Using the R11's own touchscreen.
,
Nov 28 2016
+denniskempin (but I somehow doubt it's our side). If you have specific example apps and specific repro steps that would be better to track down.
,
Dec 14 2016
The app from #0 does behave oddly in fullscreen mode (using M56). We haven't seen this with other apps. 0spore, can you give more examples of apps which have behaved badly?
,
Jan 25 2017
Adlr@ please triage and reassign as suitable.
,
Jan 28 2017
I am seeing the same behaviour on all my ARC apps since about last August or September. Have to click down and to the right of buttons in any dialogues or menus. Usually the main screen of the app works correctly though, it only happens when something pops up. That's independent whether the app runs full screen or not. Chromebook Pixel (2013). A few other issues that seem related: 634314 654740 628543 637553 645850
,
Jan 30 2017
#10, if you are talking about chromebook pixel 2013, that's something different. This bug is about the Play on chromebook feature which is not available on pixel 2013.
,
Jan 31 2017
#11, okay sorry since this was under ARC I was under the impression it refers to the ARC that's also available on previous devices. Is ARC++ referring to the Play on chromebook, whereas ARC (without the ++) refers to the older technology? Thanks.
,
Apr 5 2017
,
Apr 5 2017
,
Jan 10 2018
|
|||||||||||
►
Sign in to add a comment |
|||||||||||
Comment 1 by luxte...@gmail.com
, Oct 11 20161.8 MB
1.8 MB View Download