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

Issue 825767 link

Starred by 3 users

Issue metadata

Status: Untriaged
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: ----



Sign in to add a comment

Device Home screen intensity be changed, after open Baidu website.

Reported by gracetc_...@asus.corp-partner.google.com, Mar 26 2018

Issue description

Device name: Nexus 6P and Asus device with Android 8.0

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

URLs (if applicable):
m.baidu.com

Steps to reproduce:
1. Open m.baidu.com by Chrome App
2. When alert "baidu want to use your device's location" come out, DON'T click ALLOW or BLOCK. 
3. Click Home key. Check the screen intensity of Home

Expected result:
The screen intensity of Home won't be changed.


Actual result:
The screen intensity of Home become dark.

More information :
If remove Chrome app from recent app, then screen intensity of Home return to normal.
It seems can't reproduce on Android 8.1 , but it can reproduce on Android 8.0 device. Is it a AOSP bug ? How can we fix it ?
Attached Google bug report for your reference.

Thanks for your help
 
bugreport-WW_Phone-OPR1.170623.026-2018-03-26-17-28-12.zip
4.3 MB Download
Labels: Needs-triage-Mobile
Cc: sandeepkumars@chromium.org
Components: UI
Labels: FoundIn-66 Triaged-Mobile M-67 FoundIn-67 FoundIn-65
Status: Untriaged (was: Unconfirmed)
Tested the issue in Android. Below are the observations.

Steps:
1. Navigated to m.baidu.com 
2. DON'T click ALLOW or BLOCK on the location permission bubble
3. Click Home key. Check the screen intensity of Home

Device used:
Nexus 6P

OS Versions
7.1.2 and 8.1.0

Note:
1. Issue is not seen in 8.1.0
2. Issue is seen in 7.1.2

Observing inconsistency in reproducing this issue in other builds, hence marking as untriaged for further inputs.

Please navigate to below link for log's, sample file generated and screen shot--
go/chrome-androidlogs/825767

Thanks!!

Issue 827233 has been merged into this issue.
Hi Chromium helper,

Thanks for your help , I can't see the detail in issue 827233.
Would you help check how do this issue plan to fix. Fix on Chrome or AOSP?
If it's an AOSP fix, please advice the change. Thanks.

Sign in to add a comment