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

Issue 880007 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Oct 15
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Floating keyboard bottom bar got a opaque background.

Project Member Reported by iloahz@chromium.org, Sep 3

Issue description

Chrome Version: 70.0.3508.0
OS: Chrome OS

What steps will reproduce the problem?
(1) Open floating keyboard.
(2) Leave it there a while.
(3) Drag it to overlap with the shelf, check bottom bar part.

I can not repro this consistently, but this did happen quite some times.
Above repro step is just my guess from experience.

What is the expected result?

What happens instead?
see attached screenshot.


 
non-trans-bottom.png
60.8 KB View Download
Cc: wuyingbing@chromium.org chengong@chromium.org shend@chromium.org
hi shend@, can you also help take a look?
Owner: shend@chromium.org
Status: Assigned (was: Untriaged)
Strange...seems like the window lost its transparency. I will try to use the floating keyboard more and see if I run into this bug.
Hi Darren,
Such bug repro several times.
Could you add a test to guard it?
Attaching some more version info:

Google Chrome	71.0.3556.0 (Official Build) unknown (64-bit)
Revision	52144a74b506cf0e896f919d12958ab7ac1cd53a-refs/heads/master@{#591961}
Platform	11028.0.0 (Official Build) dev-channel caroline test
Firmware Version	Google_Caroline.7820.384.0
I haven't been able to reproduce... Can you tell me more about how the bug happens?
Managed to repro in a very weird way...when I run an automated integration test, the UI turns opaque when I connect to the inputview.html page via the devtools websocket.

Not the best repro, but I'll see where this goes.
Well...if I run chrome with --remote-debugging-port=9222, open localhost:9222, click inputview.html and then refresh the page, the keyboard becomes opaque...

Not sure if this is the same issue that you guys are having.
Filed a bug here:  https://crbug.com/891193 
Status: WontFix (was: Assigned)

Sign in to add a comment