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

Issue 778297 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Oct 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: ----



Sign in to add a comment

Black blocks on some websites

Reported by ajaysing...@gmail.com, Oct 25 2017

Issue description

Device name: Xiaomi Mi4i

From "Settings > About Chrome"
Application version:
Operating system: 5.0.2 LRX22G

URLs (if applicable):www.quora.com

Steps to reproduce:
(1) Open quora.com
(2) login and reach feed
(3) scroll down

Expected result: smooth srolling with proper webpage display


Actual result: webpage is covered partially with big black blocks and scrolling is also slow




 

Comment 1 Deleted

Labels: Needs-triage-Mobile
Cc: msrchandra@chromium.org nyerramilli@chromium.org ligim...@chromium.org sandeepkumars@chromium.org
Labels: TE-NeedsTriageFromMTV
Tested the issue in Android and could not reproduce the issue.

Steps Followed:
1. Launched Browser
2. Navigated to quora.com
3. Logged in with valid credentials
4. Scrolled down the page and no black blocks are observed.

Chrome versions tested:
61.0.3163.98

OS
Android 5.0.0

Android Devices 
5.0.0:; Micromax A106 Build?LRX21M

Requesting MTV team to take a look on this issue as 5.0.2 LRX22G Xiaomi Mi4i device is not available with clank-hyd team.

Thanks!!
Labels: -TE-NeedsTriageFromMTV Needs-Feedback
Thanks for your report! We couldnt repro this issue on latest Chrome 61.0.3163.98.
Can you please provide below details for further triaging?
1. Chrome Version
2. Screenshot and bug report (if possible)

How to take a bug report on Android devices:

'Settings' -> 'Developer options' -> 'Take bug report'

Note:
You must have developer settings enabled.

Enable developer settings:

Go to the settings menu, and scroll down to "About tablet” or “About phone.” Tap it.
Scroll down to the very bottom, where you see "Build number." 
Tap the build number seven (7) times. After the third tap, you'll see a dialog that says you're four taps away from being a developer. On the seventh tap, you’ll see a dialog that says developer setting are enabled.

I just tried reproducing the error in Chrome beta and couldn't. Seems like the issue is fixed somehow. Thanks for the proactive support guys :)
Project Member

Comment 6 by sheriffbot@chromium.org, Oct 27 2017

Cc: rsgav...@chromium.org
Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "rsgavara@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Labels: Triaged-Mobile
Status: WontFix (was: Unconfirmed)
@ajaysinghajay11 -- Thank You for the update.
Marking the issue as Won't Fix as per Comment# 5. Please feel free to raise a new bug if the issue is again seen.

Sign in to add a comment