New issue
Advanced search Search tips

Issue 901760 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Nov 14
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Black box appears in center of every tab - turns into invisible box after deactivating hardware acceleration

Reported by alexande...@googlemail.com, Nov 5

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.77 Safari/537.36

Steps to reproduce the problem:
1. No idea
2. 
3. 

What is the expected behavior?
No box!

What went wrong?
 After updating chrome, a black box appeared in the center of my browser content area. After some self help (deactivating the hardware acceleration), the black box turned into an invisible box, but that box is still blocking all mouse inputs in the center of my screen, which is super annoying. Other fixes, e.g. malware checks, new profile, basically everything that was suggested in forums didn't help. 

Did this work before? Yes the version before the current update

Chrome version: 70.0.3538.77  Channel: stable
OS Version: 10.0
Flash Version:
 
Labels: Needs-Triage-M70 Needs-Bisect
Cc: phanindra.mandapaka@chromium.org
Labels: Needs-Feedback Triaged-ET
Thanks for filling the issue...

Unable to reproduce the issue on reported chrome 70.0.3538.77 and latest chrome 72.0.3602.0 using windows 10. Attaching screencast for reference.
Steps:
-----
1. Launched reported chrome 
2. Opened chrome://settings >> deactivating hardware acceleration
3. Navigated to https://en.wikipedia.org/wiki/India and https://edition.cnn.com/
As we have not observed any black boxes 

@Reporter: Can you verify this issue with fresh profile that is not having any extensions and apps or reset all the flags. Let us know whether issue still persists. Also attach chrome chrome://gpu.  
901760.mp4
17.5 MB Download
Labels: Hotlist-DesktopUIChecked
Status: WontFix (was: Unconfirmed)
**UI mass Triage**

We were unable to reproduce this bug. If this bug still reproduces for you, 
please reopen or file a new issue. Thanks!

Sign in to add a comment