New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 782122 link

Starred by 1 user
Status: Assigned
Owner:
tedc...@chromium.org
Cc:
pnangunoori@chromium.org
█ sandeepkumars@chromium.org
nyerramilli@chromium.org
ligim...@chromium.org
█ msrchandra@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Cocos2dx Touch Receiving Issue

Reported by abhyu...@icsoft.in, Nov 7 2017 
Device name:All devices

From "Settings > About Chrome"
Application version:
Operating system:Android 7.0

URLs (if applicable):https://rummy.baadshahgaming.com/android

Steps to reproduce:
(1)Try to press any button its touch target is available beneth the button.(ex Sign up button)
(2)
(3)

Expected result:The touch should be on the button.



Actual result:If we touch beneth the button only the touch is listened
It was working well with the previous versions of chrome.

Comment 1 by pnangunoori@chromium.org, Nov 7 2017

Labels: Needs-triage-Mobile

Comment 2 by pnangunoori@chromium.org, Nov 7 2017

Cc: msrchandra@chromium.org nyerramilli@chromium.org pnangunoori@chromium.org sandeepkumars@chromium.org
Labels: -Pri-3 Triaged-Mobile M-64 Pri-2 Type-Bug-Regression
Status: Untriaged (was: Unconfirmed)
Tested the issue in Android and able to reproduce the issue.

Steps Followed:
1. Launched the Chrome Browser.
2. Navigated to https://rummy.baadshahgaming.com/android. 
3. Switched device to portrait mode.
4. Tried to tap on the buttons “SIGN UP” or “LOG IN”.

Observations: Upon tapping on the buttons, no action is performed

Chrome versions tested:
61.0.3163.98, 62.0.3202.84, 63.0.3239.31 64.0.3260.0

OS
Android 7.0

Android Devices
7.0, SM-J710F Build/NRD90M

Below is the bisect info
=======================
Chrome Good Build -- 61.0.3136.0
Chrome Bad Build  -- 61.0.3139.0

CL for above builds: https://chromium.googlesource.com/chromium/src/+log/61.0.3136.0..61.0.3139.0?pretty=fuller&n=10000

Unable to provide the exact revision as Chrome builds are getting crashed when tried to access the URL 'https://rummy.baadshahgaming.com/android' in the Chrome builds 61.0.3137.0 and 61.0.3138.0. Hence marking this issue as untriaged.

Please navigate to below link for log's and video--
go/chrome-androidlogs/782122

Note: Unable to test this issue on Desktop as the URL is not accessible in desktop browser..

Thanks!!

Comment 3 by pnangunoori@chromium.org, Nov 7 2017

Components: UI>Browser>Core

Comment 4 by abhyu...@icsoft.in, Nov 8 2017 

I've tested it in the 60.0 its working in that,
URL which can be used is https://rummy.baadshahgaming.com/
In Chrome version from 61.0.3136.0 to 64.0.3260.0 its now working

Comment 5 by pnangunoori@chromium.org, Nov 9 2017

Cc: ligim...@chromium.org
Tested on latest Chrome Stable #62.0.3202.84, Canary #64.0.3260.0 on the following devices and couldn't reproduce the issue:

Android 7.0.99, Pixel Build/PPR1.171102.002
Android 8.1.0, Pixel XL Build/0PM1.171019.005

Comment 6 by danielpark@chromium.org, Mar 6 2018

Labels: android-fe-triaged
Owner: tedc...@chromium.org
Status: Assigned (was: Untriaged)

Comment 7 by tedc...@chromium.org, Mar 7 2018

Labels: Needs-Feedback Needs-TestConfirmation
Based on the comment in #5, does this still repro?

Seems like we can close this out?

Comment 8 by abhyu...@icsoft.in, Mar 8 2018 

This issue is only applicable for android crome versions and it still
occurs.

Comment 9 by tedc...@chromium.org, Mar 13 2018 

What versions of Chrome are you seeing this in?

Comment 10 by abhyu...@icsoft.in, Mar 15 2018 

im using chrome 65.0.3325.109
►

Sign in to add a comment