Issue metadata
Sign in to add a comment
|
Floated components hide when inside a container animated with jquery
Reported by
rhys.god...@gmail.com,
Jul 21 2016
|
||||||||||||||||||||||
Issue descriptionExample URL: Steps to reproduce the problem: Issue discovered using the Nexus 6P Physical Device option on browserstack. Don't have a physical device to hand, but this is supposed to be accurate. System info at time of report: Package Name: com.android.chrome Package version: 265701251 Package version name: 50.0.2657.12 Installed by: Process name: com.android.chrome Time: Thursday, July 21, 2016 System App: false Locale: en_US System Device: angler Build ID: NPC56P Build type: user Build fingerprint: google/angler/angler:N/NPC56P/2659757:user/release-keys Model: Nexus 6P Product: angler SDK version: 23 Release: N Incremental version: 2659757 Codename: N Board: angler Brand: google A simple reproduction of the issue can be seen here: https://jsfiddle.net/8uxf8187/1/ The panel is shown using the JQuery animate method, when it shows the floated elements are hidden. If the area is redrawn then they are shown again (e.g. scrolling/resizing etc.). This can be worked around by causing the elements to be redrawn after the animation has been finished, this has to change the CSS enough to cause the redraw (in this case I've changed the position to relative which triggers the reload without changing the effect): https://jsfiddle.net/8uxf8187/ What is the expected behavior? What went wrong? Floated elements are not shown after animation Does it occur on multiple sites: N/A Is it a problem with a plugin? N/A Did this work before? Yes Works fine in the current stable Android build (6.x) Does this work in other browsers? N/A Chrome version: 50.0.2657.12 Channel: n/a OS Version: 7 Flash Version:
,
Jul 21 2016
Unfortunately I don't have access to a device where I can upgrade Chrome to repro.
,
Jul 22 2016
Thank you for providing more feedback. Adding requester "rsgavara@chromium.org" for another review and adding "Needs-Review" label for tracking. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Aug 8 2016
,
Mar 13 2017
Cleaning up "Needs-Review" label as we are not using this label for triage anymore. Ref bug for this cleanup 684919
,
Nov 30 2017
@rhys.godfrey -- Thank You for the report. Could you please upgrade your Chrome to Latest Stable# 62.0.3202.84 and let us know if the issue is still reproducible, if yes provide us with a screen cast or a screenshot which would help us triage the issue. Thanks in Advance.
,
Dec 4 2017
,
Dec 13 2017
Closing issue due to lack of feedback requested but not provided. If the issue still exists please open a new issue with the details requested.
,
Dec 15 2017
The NextAction date has arrived: 2017-12-15 |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by rsgav...@chromium.org
, Jul 21 2016