related to https://bugs.chromium.org/p/chromium/issues/detail?id=417782?

I can't reproduce this on my pixel 2.  Can you do a video screen capture and attach it to this bug?

Tested on reported Chrome #66.0.3350.12, latest Canary #66.0.3352.3 & latest stable #64.0.3282.137 and not able to reproduce the issue on Pixel Android 8.1.0 and Samsung J7 Android 7.0.0 by following the below steps:

1. Launched Chrome browser.
2. Navigated to the URL: m.joemonster.org
3. Click on Hamburger menu.
4. Observed that menu is displayed properly. 

marcin@ -- Could you please confirm whether it is consistently reproduced or not. If reproduced please share OS details including build details.

Attached screenshot for reference.

Thanks!

Deleted: 814686.png 231 KB

	814686.png 231 KB View Download

reproducible in 100%

Deleted: Screenshot_20180223-093607.png 348 KB

	Screenshot_20180223-093607.png 348 KB View Download

marcin@ -- Could you please provide the logs reproducing the issue for the further triage as we were unable to reproduce on the reported device Pixel Android 8.0.1 Build/OPM1.171019.016 on latest Canary #66.0.3355.0 as well.

Removing the 'Needs-Bisect' label for now as issue is not reproduced at TE's end.

Thanks in advance!

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

with 66.0.3355.0 still visible for me on Android 8.1 (on 7 it's OK)

I can't duplicate this either, but I can redescribe what isn't happening correctly.

On tapping the menu a panel has the visibility and right properties toggled (right:0, visibility: visible) from (right -xxxpx, visibility: hidden).  There is a transition on both of those properties, something seems to be going wrong with that.

marcin@,szager@ - why is this blocking 417782 ?  Do you have more insight?

Is there a memory precondition to the failure?  Any more logs available? If not, we're going to need to close it as won'tfix until we can figure out how to repro, which isn't very cool.

device with bug is available, just say, what logs do you expect :D

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Not clear this is related to Root-layer-scrolls

Test Team already attempted and provided the observations in #9.Not seeing any information for further triaging.

...and I offer logs, but I need to know, how to collect them :D

marcin@ -- Please refer the below links, they may help

https://developer.android.com/studio/command-line/logcat.html
https://logmatic.io/blog/a-how-to-guide-to-debugging-with-android-logcat/
https://www.youtube.com/watch?v=P7BPxDKTHm8

Logcat logs are unlikely to be useful. What would be much more useful is a devtools performance trace; this will hopefully tell us whether some resource is not being fetched or some layer not being painted.

marcin@ - The following should hopefully capture a good timeline trace for the problem:

1. Setup your Android device to work with remote devtools (https://developers.google.com/web/tools/chrome-devtools/remote-debugging/)

2. With remote devtools setup, visit m.joemonster.org

3. In the devtools window on your desktop/laptop, open the Performance tab and click on the icon to 'Start profiling and reload page' (see screenshot 1)

4. Reproduce the problem on the device.

5. In the devtools window on your desktop/laptop, 'stop' the recording if it is still going on.

6. In the devtools window on your desktop/laptop, right click and choose 'Save Profile' (see screenshot 2)

7. Uploading the resulting file to this bug using 'Attach a file' and then 'Choose File'.



Thanks for your help marcin@, and apologies for the inconvenience. Unfortunately we've been unable to reproduce on a Pixel with Android 8.1 here so far :(.

Deleted: screenshot_1.png 439 KB

	screenshot_1.png 439 KB View Download

Deleted: screenshot_2.png 295 KB

	screenshot_2.png 295 KB View Download

cc-ing chrishtr@ as an FYI in-case this could be paint related. Chris see comment #4 for a reproduction video from the OP, unfortunately test team and ourselves have been unable to reproduce locally so far.

in 3368 it works again