ARC: clicking button and menu in android popup (menu or dialog) takes no effect
Reported by
y...@slice.com,
Sep 12 2016
|
||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.14 Safari/537.36 Platform: 8530.81.0 (Official Build) stable-channel link Steps to reproduce the problem: 1. on Chromebook pixel, install Slice app from chrome store 2. Launch the app, clicking on "LOG IN" button, then "GOOGLE BUTTON" 3. You should a a pop asking to "Select an email" or "Let me enter one". 4. Try to click on one of the option in the popup What is the expected behavior? Clicking the menu option in android poup should trigger the event to continue the work flow What went wrong? clicking menu in android popup takes no effect Did this work before? Yes 12/2015 Chrome version: 53.0.2785.103 Channel: stable OS Version: Flash Version: 22.0.0.209-r1 It worked when we uploaded the Slice app into chrome web store last December. Not sure when did it start broken.
,
Sep 19 2016
I noticed that lately in a number of ARC apps (Aquamail, MLO, ...) some clicks seem to be off by some weird offset. This happens not on the main screen of apps, but often when a menu or a dialog is opened and the user is presented with a list of items to choose, or some buttons to click. User has to click not on the button, but further below or further to the right off the item to actually click it. The offset seems to vary from app to app, I haven't found a specific rule. So, in summary, in a lot of dialogs and menus, user has to point the mous down and right of an item to actually click it. This affects numerous apps (both from Store and self-converted).
,
Oct 4 2016
Btw, it is possible to actually select menu or dialog items with cursor keys and then press enter key. It's just the mouse click that is off and you cannot reach the buttons you are intending to click with the mouse.
,
Oct 4 2016
I think this is related to Issue 637553 .
,
Oct 4 2016
May also be related to Issue 634314.
,
Feb 27 2017
This issue is no more reproducible in the latest build. If still an issue please reopen |
||
►
Sign in to add a comment |
||
Comment 1 by abodenha@chromium.org
, Sep 15 2016