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

Issue 626244 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: Aug 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 3
Type: Bug

Blocking:
issue 558575



Sign in to add a comment

Scroll Anchoring: wrong scroll position on Tweetdeck when going back to timeline

Project Member Reported by kenjibaheux@chromium.org, Jul 7 2016

Issue description

Version: 54.0.2790.0 (Official Build) canary (64-bit)
OS: Mac OS X

What steps will reproduce the problem?
(1) Go to https://tweetdeck.twitter.com/
(2) Scroll one of the timeline (column)
(3) Click any tweet
(4) Hit the back arrow to go back to the timeline

What is the expected output?
Scroll position on the timeline is unchanged.

What do you see instead?
Scroll position on the timeline is changed.

Please use labels and text to provide additional information.

 
Blocking: 558575

Comment 2 by ymalik@chromium.org, Aug 11 2016

I can't repro this issue because tweetdeck is down for me.

But sounds like what you're seeing is already something we'd expect (As of V1 implementation of scroll anchoring see comment #9 on  issue 594879 ). 

Say that you're at scroll position x before reloading the page. Right after you reload the page, we will be at position x, but what you see at position x after the refresh can be different from what you see before the refresh because scroll anchoring will keep your current anchor node in the viewport, and as a result, change the scroll offset yielding different content in the viewport once the page is fully loaded.

I'd like to double check that's actually what's going on. Can you still repro it on the page? Can you repro this on other pages? 
I could not repro anymore.
There seems to be some sort of hiccup going while scrolling a timeline though. Will check without SA.
Note: there is no reload involved, the back arrow is a UI element in Tweetdeck, not the back button / ...
Status: WontFix (was: Assigned)
I think we are good here. Closing.

Sign in to add a comment