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

Issue 795618 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: 2018-01-25
OS: Android
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Android: Weird scrolling behavior after pushing back button

Project Member Reported by wfh@chromium.org, Dec 17 2017

Issue description

Chrome Version: 65.0.3295.0 (Official Build) canary (32-bit)
OS: Android 8.1.0; Pixel XL Build/OPM1.171019.011

What steps will reproduce the problem?
(1) visit Reddit.com
(2) scroll down to a link to e.g. imgur.com, maybe half way down the page and click on link
(3) push back and then wait for the page to fully loaded again.
(4) scroll the page using finger

What is the expected result?

Page scrolls from where you are at

What happens instead?

Page scrolls from a random place above

Please use labels and text to provide additional information.


For graphics-related bugs, please copy/paste the contents of the about:gpu
page at the end of this report.

 

Comment 1 by wfh@chromium.org, Dec 18 2017

Does not happen in Dev: 64.0.3282.29 (Official Build) dev (32-bit)
Labels: Needs-triage-Mobile
Cc: sandeepkumars@chromium.org
Labels: Triaged-Mobile Needs-Feedback
Tested the issue in Android and could reproduce the issue. Observed the above mentioned error message

Steps Followed:
1. Launched Chrome Browser.
2. Navigated to Reddit.com
3. Scrolled down to a link to e.g. imgur.com
4. Pushed back and then wait for the page to fully loaded again
5. Observed the page is scrolling from where we are

Chrome versions tested:
65.0.3295.0

OS
Android 8.0.0

Android Devices
8.0.0; Pixel XL Build/OPR1.170623.027

@wfh: Could you please find the above observations and help us with a screencast for further triaging of the issue.

Thanks!!

Comment 4 by bokan@chromium.org, Jan 4 2018

Cc: bokan@chromium.org
#3, did you mean you could *not* reproduce the issue?

I also cannot repro 65.0.3310.0 on a Pixel 2 XL

Comment 5 by bokan@chromium.org, Jan 11 2018

NextAction: 2018-01-18
Ping,

sandeepkumars@, please confirm.

wfh@, can you still repro this? Is the repro reliable or occasional?
The NextAction date has arrived: 2018-01-18

Comment 7 by bokan@chromium.org, Jan 18 2018

Status: WontFix (was: Untriaged)
Closing due to lack of repro or additional details. Feel free to chime in if this is still occurring and we can take another look.

Comment 8 by wfh@chromium.org, Jan 28 2018

Labels: ReleaseBlock-Stable M-65
Status: Available (was: WontFix)
This is now happening in Dev 65.0.3325.16 (Official Build) dev (32-bit)

Comment 9 by wfh@chromium.org, Jan 28 2018

Dev variations

bd23585d-f23d1dea
c0c84556-a48559fc
45514eb0-77afc4fd
8b81f22b-3f4a17df
d6f3e6fe-f23d1dea
6a89113b-8842e68f
16e0dd70-3f4a17df
da89714-4ad60575
9041608a-3f4a17df
1e528f0f-15305a2
b130ecb8-2e32ee7e
ca05d627-3f4a17df
d175604-65bced95
7e6cf017-f23d1dea
c4c991b6-f23d1dea
1949605e-f23d1dea
45df7875-ca7d8d80
6952a2eb-84683465
eadd2b9b-3fcf2767
cf55e4c6-f23d1dea
63986311-ca7d8d80
e9ee300f-cd19cd38
a0930725-4d2fac87
d52c4ff7-d52c4ff7
3eb101d6-f23d1dea
8303c047-65bced95
236d5d9e-768105e1
bd007046-3f4a17df
47e5d3db-3d47f4f4
77207729-e0e232cc
1c752ce9-1c752ce9
c3d1d2ca-3f4a17df
baaf4db5-612a79a3
19c1fdaf-3d47f4f4
3042ad4b-cf4f6ead
57f575bb-f23d1dea
5e3a236d-59e286d0
9773d3bd-720b026c
93731dca-e89d496c
8e3b2dc5-93702590
c157e591-65bced95
9e5c75f1-8a522f40
85663a5d-85634f4c
2981bcb4-3d47f4f4
3de1fbf2-3f4a17df
f79cb77b-3f4a17df
d1d8d202-db9e7dc4
2c45a3a5-afa0e1d2
4ea303a6-1e6a8d9b
bcc34a89-72e77f72
6e6e0c7e-f23d1dea
d92562a9-ea77f3c1
2b33233e-d8253d6f
14c5a050-ca7d8d80
6973a1cf-3f4a17df
72606c4f-f23d1dea
58a025e3-c2b41702
4932440-f23d1dea
757a5d98-28165b59
30ab2dd8-cf4f6ead
b2f0086-870290a7
2d871858-3f4a17df
344833e9-473e8c2e
3f273a97-e3ad1896
4bc337ce-614c45d0
9a2f4e5b-5af84bc7
494d8760-3f4a17df
3ac60855-3ec2a267
4442aae2-7158671e
ed1d377-e1cc0f14
75f0f0a0-a5822863
e7e71889-4ad60575
34baa302-c306c9a2
f5fff3a2-3f4a17df
bbb8f811-3f4a17df
9cade933-f23d1dea

Can no longer repro in canary 66.0.3333.0 (Official Build) canary (32-bit)

Canary variations

bd23585d-f23d1dea
c0c84556-a48559fc
45514eb0-612a79a3
8b81f22b-3f4a17df
d6f3e6fe-f23d1dea
6a89113b-8842e68f
853359fa-3f4a17df
16e0dd70-3f4a17df
61fba06-ca7d8d80
da89714-4ad60575
9041608a-3f4a17df
1e528f0f-3b7f37f3
b130ecb8-2e32ee7e
6025934e-3f4a17df
1949605e-502783f4
e9ee300f-cd19cd38
ce38b0fc-3f4a17df
d52c4ff7-f23d1dea
3eb101d6-3f4a17df
8303c047-65bced95
236d5d9e-ca7d8d80
bd007046-3f4a17df
47e5d3db-3d47f4f4
77207729-e0e232cc
c3d1d2ca-f23d1dea
baaf4db5-612a79a3
19c1fdaf-ca7d8d80
3042ad4b-f23d1dea
121ae2bc-ee24275d
267255c3-ab59f10a
57f575bb-f23d1dea
1f56023b-f23d1dea
ef05a96e-e72f323d
93731dca-e89d496c
8e3b2dc5-93702590
c157e591-65bced95
9e5c75f1-8a522f40
85663a5d-85634f4c
2981bcb4-3f4a17df
3de1fbf2-f23d1dea
f79cb77b-3f4a17df
d1d8d202-db9e7dc4
2c45a3a5-afa0e1d2
4ea303a6-bc20e0f9
b19465ab-a79d803f
6e6e0c7e-3f17a7d8
d92562a9-ca7d8d80
2b33233e-881ca6c9
14c5a050-ca7d8d80
6973a1cf-f23d1dea
72606c4f-3f4a17df
4932440-f23d1dea
757a5d98-215a0907
30ab2dd8-f23d1dea
b2f0086-870290a7
2d871858-f23d1dea
344833e9-1525b35b
3f273a97-25a103a9
4bc337ce-535cb40a
9a2f4e5b-17af0913
494d8760-3f4a17df
3ac60855-3ec2a267
4442aae2-7158671e
ed1d377-e1cc0f14
75f0f0a0-d7f6b13c
e7e71889-e1cc0f14
f5fff3a2-f23d1dea
bbb8f811-f23d1dea


Comment 10 by wfh@chromium.org, Jan 28 2018

Actually I take that back, it's still happening on Canary.

Comment 11 by bokan@chromium.org, Jan 29 2018

wfh@, does this always happen or is it occasional? If occasional, about how often? I can't repro locally - is there anything else you think might be involved in reproducing?
wfh@, are you still seeing this issue?

Comment 13 by cmasso@google.com, Feb 14 2018

Owner: bokan@chromium.org
Status: Assigned (was: Available)
 bokan@ are you looking into this issue?

Comment 14 by bokan@chromium.org, Feb 14 2018

Unfortunately, without more details or information this isn't very actionable. wfh@, is this still occurring?

Comment 15 by bokan@chromium.org, Feb 14 2018

A trace of the issue when it happens might also help shed some light. https://www.chromium.org/developers/how-tos/submitting-a-performance-bug

Comment 16 by bokan@chromium.org, Feb 15 2018

Labels: -ReleaseBlock-Stable
NextAction: 2018-01-25
Removing RBS since we haven't been able to repro and haven't gotten additional information, we also haven't seen similar issues reported from elsewhere. 

Sign in to add a comment