Issue metadata
Sign in to add a comment
|
[Chrome][V66][Android 8.0] Chrome doesn't change its configuration in accordance with device display configuration change
Reported by
seiyon.p...@gmail.com,
May 3 2018
|
||||||||||||||||||||
Issue descriptionSteps to reproduce the problem: 1. Settings > Application > Chrome > Force stop 2. Settings > Display > Screen resolution > Set low 3. Open up Chrome and go to "naver.com" 4. Open Settings from recent app list 5. Settings > Display > Screen resolution > Set high 6. Open Chrome from recent app list 7. Try to touch any contents on "naver.com" What is the expected behavior? What went wrong? Touch doesn't work. Did this work before? Yes V63 Chrome version: 66.0.3359.139 Channel: stable OS Version: 8.0 Flash Version: It's not reproducible on Nexus because Nexus doesn't provide "Screen resolution" change feature. It's reproducible on Joan which provide "Screen resolution" change feature. FYI, when user changes the setting in "Screen resolution", device implementation broadcasts android.intent.action.CONFIGURATION_CHANGED, but it seems that Chrome doesn't change its configuration accordingly.
,
May 3 2018
,
May 4 2018
,
May 4 2018
seiyon.park@ -- From the Bugreport, we can observe that issue is observed on LGE Joan model v8.0.0. Could you please share the market details of the model. So that we can pick and work on the respective device. Thanks!
,
May 9 2018
pnangunoori@chromium.org I'm assuming that you prefer to Joan model launched in USA and sharing the Joan Verizon model. - Device name : joan - Product name : joan_vzw - Marketing name : V30 - Model name : VS996 https://www.verizonwireless.com/smartphones/lg-v30/
,
May 9 2018
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
May 10 2018
Adding the label 'TE-NeedsTriageHelp' as the device doesn't seems to be available with India and MTV teams. Thanks!
,
May 14 2018
,
May 14 2018
You say this worked in M63, but is now broken in M66? It will be hard to recreate this without the device. How does the LG implementation of screen resolution differ from: Android Settings > Accessibility > Display size on Stock Android? +mthiesse who added special handling for the density (https://chromium-review.googlesource.com/c/chromium/src/+/668042), but that works on stock Android and also landed primarily in 63, so I'm wondering about the regression range.
,
May 15 2018
Seems unlikely to me to be density, as we call recreate manually when not in VR. Maybe handling sizeChanged is going wrong somehow? Maybe we're caching things we shouldn't be, and expecting size to only change with orientation or something? These are purely guesses. I'm on vacation, but you might try reproducing using 'adb shell wm size' Ted?
,
May 15 2018
+Needs-Feedback. We either need the device to verify locally or more feedback from the original reporter.
,
May 18 2018
Dear Chrome team 1. How does the LG implementation of screen resolution differ from (Comment 9) I have no idea on how to implement the screen resolution change. But if you let us know what event recreates Chrome, we will be able to check if changing "Screen resolution" send that event or not. 2. To check if android.intent.action.CONFIGURATION_CHANGED recreates Chrome We thought "Screen resolution" broadcasts android.intent.action.CONFIGURATION_CHANGED and it recreate Chrome. So please check Chrome works in accordance with the intent and let us know if we misunderstood. 3. To provide the device I'm afraid we couldn't provide the device, so please let me circle back to you with reproducible way like adb command.
,
May 18 2018
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by seiyon.p...@gmail.com
, May 3 201810.0 MB
10.0 MB Download