Issue metadata
Sign in to add a comment
|
Chrome url texts are not selectable using the mouse and the omnibox is getting messed up while selecting |
||||||||||||||||||||||||
Issue descriptionThis report will ONLY be viewable by Google. Device name: Samsung S7 Edge Android version:NRD90M Chrome : 59.0.3071.112 Precondidtion:- THIS ISSUE REPRO ONLY WHEN PHYSICAL MOUSE/KEYBOARD TO THE DEVICE OR THIS ISSUE CAN REPRODUCED USING USING SAMSUNG DEX WITH S8 Steps to reproduce: (1) download and install the above chrome build (2) Launch chrome > Input > some url > Select the text/url using the mouse Actual result: -Chrome url texts are not selectable using the mouse and the omnibox is getting messed up while selecting Additional info:- -Attaching video/bugreport/logcat
,
Jun 26 2017
logcat/bugreport/video -> http://go/chrome-androidlogs1/6/735761
,
Jun 29 2017
Can someone on the testing team with an Android keyboard try to reproduce this? May require a particular Samsung device too; it's not clear.
,
Jul 6 2017
acindhe@, can you check this?
,
Jul 12 2017
This is a regression issue, repro on all the devices. Please find the bisect info below Good build: 59.0.3071.105 Bad Build: 59.0.3071.106 Bisect range: https://chromium.googlesource.com/chromium/src/+log/59.0.3071.105..59.0.3071.106?pretty=fuller&n=1000 Note: in the above bisect range we see all the commits number is same i.e. 464641 Suspected CL: https://chromium.googlesource.com/chromium/src/+/ee6875ffe6968088524858933110e7609b29be16 aelias@ Could you please look into this issue, if its not related to your change, could you please assign to respective owner. Thanks
,
Jul 12 2017
,
Jul 13 2017
I have tried on M60 & M61 builds. On M60 the issue repro after branch cut. Please find the bisect info below for M60 Good build: 60.0.3112.35 Bad build: 60.0.3112.36 For M61: Good build: 61.0.3132.0 Bad build: 61.0.3133.0 Bisect range: https://chromium.googlesource.com/chromium/src/+log/61.0.3132.0..61.0.3133.0?pretty=fuller&n=1000 Good Commit: 480084 Bad commit: 480085 Culprit CL : https://chromium.googlesource.com/chromium/src/+/b58f576ba586c18986315cb80e9b70fc8de5f71a amaralp@ It looks like related to your change, could you please look into this issue. Thanks
,
Jul 20 2017
,
Jul 20 2017
I think this must have the same root cause as http://crbug.com/740855 . The only way the culprit patch could be causing this bug is if clicks on the URL-bar are improperly getting forwarded to the content area. So this is an unexpected interaction with the preexisting problem.
,
Jul 20 2017
Note that even the clicks slightly below the top bar are affected in N, see Issue 740855 #c8.
,
Jul 20 2017
Assigning to Jinsuk and targeting to M61 due to connection with http://crbug.com/740855
,
Jul 26 2017
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by dneelame...@chromium.org
, Jun 26 2017