Issue metadata
Sign in to add a comment
|
Bottom row of nytimes mini crossword keyboard does not work |
||||||||||||||||||||||
Issue descriptionChrome Version: 66.0.3338.0 (Official Build) canary (32-bit) OS: Android 8.1.0; Pixel XL Build/OPM1.171019.012 What steps will reproduce the problem? (1) visit https://www.nytimes.com/crosswords/game/mini (2) type in bottom row of virtual keyboard (3) What is the expected result? Letters appear What happens instead? Nothing. Please use labels and text to provide additional information. Works fine in Stable 64.0.3282.137. I have chrome home enabled. For graphics-related bugs, please copy/paste the contents of the about:gpu page at the end of this report.
,
Feb 6 2018
Also manifests in latest Canary - 66.0.3340.3 (Official Build) canary (32-bit)
,
Feb 7 2018
,
Feb 8 2018
Still happening in latest build: 66.0.3342.3 (Official Build) canary (32-bit)
,
Feb 8 2018
Bisect range is 3325..3338
,
Feb 8 2018
,
Feb 8 2018
Tested the issue in Android and able to reproduce the issue. Steps Followed: 1. Launched the Chrome 2. Navigated to https://www.nytimes.com/crosswords/game/mini 3. Observed bottom keys on the keyboard isn't working Chrome versions tested: 66.0.3342.3 OS: Android 8.1.0; Pixel XL Build/OPM1.171019.016 Android Devices: Pixel XL Using the per-revision bisect providing the bisect results, Good build: 66.0.3335.0 Bad build: 66.0.3336.0 You are looking for a change made after 533277(GOOD), but before 533278(BAD). CHANGELOG URL: The script might not always return single CL as suspect as some perf builds might get missing due to failure. https://chromium.googlesource.com/chromium/src/+/ef3f05dd13ef8e10c3084e216472622912cdb1a1 From the CL's above, assigning the issue to the owner concerned. @sahel: Could you please look into the issue, and assign it to concerned owner if this is not related your change. Please navigate to below link for log's and video-- go/chrome-androidlogs/809364 Note: This issue is not observed in Desktop. Thanks!
,
Feb 8 2018
,
Feb 8 2018
Issue 810204 has been merged into this issue.
,
Feb 8 2018
https://chromium-review.googlesource.com/c/chromium/src/+/907412 should fix it. wfh@ could you please check it on ToT?
,
Feb 8 2018
https://chromium-review.googlesource.com/c/chromium/src/+/907412 landed in 66.0.3343.0. I can confirm this issue is fixed in that version. Thanks! |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by wfh@chromium.org
, Feb 6 2018