Issue metadata
Sign in to add a comment
|
Paned animation on reddit.premii.com is janky going back
Reported by
dharm...@gmail.com,
Apr 7 2016
|
||||||||||||||||||||||||
Issue descriptionSteps to reproduce the problem: I am consistently able to reproduce this on Galaxy S6, Marshmallow, chrome 49/50. I did hard reset my device and only restored app from google backup. 1. Go to reddit.premii.com 2. Click on comments 3. Click back ----- Behind the scene: Content is hidden using display none. on back. (Javascript): 1. apply display block to hidden content 2. Using settimeout wait for 10 ms 3. Settimeout callback animates content using requestAnimationFrame. Settimeout used to take roughly 12-20ms. Now it takes 300-400ms. If you don't apply display block, it will take 10-12ms. ----- This is not reproducible on Galaxy S6 + Marshmallow + Samsung Internet browser, or Webview (version 44). What is the expected behavior? Display block on hidden content used to take 1-2 ms. What went wrong? Display block on hidden content now takes 100-400ms based on the content size Did this work before? Yes It works on non-marshmallow device. On Marshmallow, chrome 44 works fine too. Chrome version: 49.0.2623.110 Channel: stable OS Version: 6 Flash Version:
,
Apr 7 2016
Is there a user-visible symptom of this? I can't observe any visible jank when following the repro steps on 51.0.2695.0. I'm wondering if that's because I failed to repro. It would be helpful if you could upload a video of the symptom.
,
May 24 2016
Yes this is a user-visible symptom. If content is loaded and hidden using CSS display: none, and want to make it visible, it take 100-400ms to make it visible. So it takes roughly 100-400ms to just to show content. I am not sure how to record this or get timeline. You can test the steps with inspector open. You will see see logs of how long it takes in those steps. Compare the same with older version of chrome (v44).
,
Jan 24 2017
OK, on a second look, I can repro the animation on reddit.premii.com being really janky going back on my Galaxy S7, but not on a Nexus 6P. Chrome version from 54-58 seems irrelevant, only the device affects it.
,
Jan 25 2017
Trace shows 287ms spent on AccessibilityMsg_Events_ACK as well as about 500ms of untraced time in TaskQueueManager::RunTask a bit earlier that I suspect may also be accessibility-related. The difference between devices is that I had https://play.google.com/store/apps/details?id=com.irishin.buttonsremapper installed and turned on in Settings->Accessibility. It has permissions "Monitor your actions" and "Observe text you type".
,
Mar 27 2017
,
Apr 21 2017
,
Apr 21 2017
,
Aug 7 2017
,
Oct 26 2017
,
Dec 7
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by rsgav...@chromium.org
, Apr 7 2016Status: Assigned (was: Unconfirmed)