Thanks for filing the issue...

The issue seems to be related to Android, hence adding appropriate labels for further triaging of the issue.

There is nothing in this example that is using the DeviceOrientation or ScreenOrientation APIs to explicitly react to device rotation. This must be an issue related to layout or compositing that is triggered by having the Chrome app change from portrait to landscape. I cannot reproduce this on 72.0.3626.14. 

Tested this issue on Pixel 2 using chrome #71.0.3578.80 and unable to reproduce this issue as per below steps

Steps:
1.Navigated to https://output.jsbin.com/sicibol/1
2.Rotated device clockwise & anti-clockwise nearly 2-3 times but no content disappearing is observed.

@cjennhong: Could you please provide device details & screen cast of the issue for further triaging. 

Thanks!

hi jbanavatu, please find the file attached.

Thanks

Deleted: test1.mp4 2.2 MB

	test1.mp4 2.2 MB View Download

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

Tested the issue in Android and able to reproduce the issue. 

Steps Followed:
1.Navigated to https://output.jsbin.com/sicibol/1
2.Rotated device clockwise & anti-clockwise 
3.Observed content is disappeared.

Chrome versions tested:
71.0.3578.98 , 73.0.3639.0(canary)

OS:
Android 8.1.0

Android Devices:
Nexus 6p

Unable to provide per-revision bisect as we are getting all good builds and getting 'You are looking for a change made after 593189(GOOD), but before 593399(BAD)". Tried to run bisect with above mentioned range i.e;593189(GOOD) & 593399(BAD), but was getting Exception: We don’t have enough builds to bisect.

Hence providing the manual bisect results,
Good Build - 71.0.3557.2
Bad Build - 71.0.3559.2

Leaving this issue as untriaged for someone from dev team to look into it . Adding RB stable for M71 please undo if not the case.

Thanks!

Not clear to me it's a layout issue - I'll take a first look today to see where the issue lies and whether it's severe enough to warrant RBS (71 is already shipping)

I've further reduced the example URL: https://output.jsbin.com/keqesuy

Strangely, making the viewport width any less than 955 makes the bug disappear. Greater values continue to reproduce. This is on a Pixel2XL - I'm guessing the value may be screen size dependent, perhaps a clue.

I think it's a paint invalidation issue since toggling background color causes everything to appear again.

-RBS since rotation on normal pages seems to work, unless we get additional reports that this is more than an edge case I'd leave it as such.

Over to chrishtr@ to triage.

The NextAction date has arrived: 2018-12-20

any update?

I'll at least look through the change list to see what might be to blame.