Issue metadata
Sign in to add a comment
|
Omnibox alignment misplaces on scrolling down the content suggestion in NTP |
||||||||||||||||||||
Issue descriptionApp Version: 65.0.3325.29 Beta iOS Version: 11.2.2 Device : iPhone X Steps to reproduce: 1. Launch chrome canary. 2. Load few content suggestions in NTP. 3. Scroll the content suggestions upwards. 4. Tap on omnibox. 5. Scroll down the content suggestions downwards. Observed results: Omnibox is misaligned for few seconds. Expected results: Omnibox should be in fixed position. Number of times you were able to reproduce: 5/5 Bug reproducible after clean install: Yes Bug reproducible after clearing cache and cookies: Yes Bug reproducible on Chrome Mobile on Android: NA Bug reproducible on Dolphin/Safari/Firefox: NA Bug reproducible on current stable build (App Version, iOS Version): No in M64 Bug reproducible on the current beta channel build (App Version, iOS Version): Yes in M65 Link to Video : https://drive.google.com/file/d/1iALvotj05iBdOG2ltqHOD0fEd9COpREn/view?usp=sharing
,
Jan 30 2018
This is actually linked to the clean toolbar. Disabling it fixes the bug.
,
Jan 30 2018
This is because the animations when contracting the omnibox are starting, and the header view is also updated with the animations, so it takes the animation time to be where it should be. Just starting then stopping the animations for the contraction as we do in the expand part doesn't work, some ContentSuggestions cells are redrawn on top of other, creating a broken effect. A possible fix would be to use some orchestrator pattern and have two different code path: the animated code path where the event are put inside the animators and the non-animated code path where the changes are directly called without having animators. I don't have time to do it now as in implies to rewrite most of the animations. sczs@, justincohen@: Do you think it should be prioritized?
,
Jan 30 2018
I don't think we should rewrite most of the animations right now. Perhaps after refresh?
,
Jan 30 2018
Just to be clear we need to change the way how animations are handled right? Not rewrite the actual animation code. Something like this CL could work as a workaround, maybe? https://chromium-review.googlesource.com/c/chromium/src/+/818489 In any case I don't think fixing this is high priority. But eventually I agree with gambard@ and we should have some sort of Orchestrator that help us deal with animations timing.
,
Jan 30 2018
,
Jan 31 2018
It is broader than the CL you linked as all the elements currently added to the animator should occur, just not in an animation block. It is indeed how the animations are handled, there is no problem with the animations. I am marking this bug available as I don't plan to fix it. For the Adaptive Toolbar I will give the Orchestrator a try and see if it is solving the problem.
,
Sep 27
I can't reproduce this post refresh, is this still an issue?
,
Oct 11
Is someone able to reproduce? |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by pkl@chromium.org
, Jan 29 2018Components: UI>Browser>Omnibox
Owner: stkhapugin@chromium.org
Status: Assigned (was: Untriaged)