Shop strip is moved to the left after returning to page |
|||||
Issue descriptionDevice name: s7 From "Settings > About Chrome" Application version:canary 66.0.3344.0 Operating system:s7 URLs (if applicable):google.com Steps to reproduce: (1)search for something, what display shop values (like "small atx cover") (2)move right with shop values (3)click on shop value (4)click Back Expected result: shop strip is displayed exactly in the same horizontal position Actual result: shop strip is moved to the left; on FF it works fine and it seems more than bug than FR.
,
Feb 12 2018
Tested the issue in Android and able to reproduce the issue. Similar behavior is observed since Chrome #60.0.3072.0 Steps Followed: 1. Launched the Chrome Browser. 2. Search for any product to purchase. 3. Scroll towards right. 4. Tap on any product. 5. Tap on device back button. 6. Observed that suggestions list is displayed from first and user has to scroll towards right to view the earlier tapped product. Chrome versions tested: 60.0.3072.0, 64.0.3282.140(Stable), 66.0.3344.0(Canary) OS: Android 8.1.0 Android Devices: Pixel XL This seems to be a Non-Regression issue as same behavior is seen since M59. Untriaged for further input's on this issue. Please navigate to below link for log's and video-- go/chrome-androidlogs/811126 Note: 1. This issue is not observed in Desktop. 2. Issue is not observed on FireFox mobile version. Thanks!
,
Feb 13 2018
Curiously, I can't reproduce this on a Pixel 2, Chrome 64.0.3282.137. Pressing back brings back the previous search result with the selected product in the same place.
,
Feb 13 2018
Re #3 - I'm also not able to reproduce on a regular Pixel on Chrome 66.0.3345.0. I'm a bit surprised that the carousel scroll position is retained after a back navigation. Is this information encoded in the URL? This got swept up in the frontend triage rotation due to the component, but the frontend team doesn't really own the navigation stack so I'm not quite sure how to route this. +clamy@ - it looks like you've been active in this component recently.. any idea which team this should go to?
,
Feb 13 2018
This seems similar to issue 500260 which was fixed by r515279 that initially landed in 64.0.3264.0. Is it possible that this is a dupe?
,
Feb 13 2018
Actually, #c5 can be probably ignored - I've missed that this issue still repros in some M66 configurations.
,
Feb 14 2018
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by pnangunoori@chromium.org
, Feb 12 2018