I tried this in both Beta (61.0.3163.60) and Canary (62.0.3194.0) with flags cleared and the position: absolute bars are correct for me, the 100vh one is larger than the initial viewport, the 100% is the same size. Hiding the URL bar doesn't resize either.

I do see an issue with the position: fixed vh bar. It should be the same size as the position: fixed % bar, and it should resize with the URL bar. It looks like it's being sized in the same way as the position: absolute.

Is this what you're seeing or do the position: absolute bars also resize? 

I see the issue with regular (static) elements. Here for example: http://strize.io/ the header (logo + animation which will make your device heat) is 100vh. On scroll it's being resizes in current Chrome Beta on Android. It isn't resized in either Safari iOS/Firefox Android/Chrome Stable Android.

Strange, I'm not seeing anything resize on that page in Beta/Dev/Canary and the behavior looks identical to Stable. I'll double-check on a second device shortly. In the mean-time, could you make sure you reset all flags in chrome://flags

Made a reset and still the the issue. Attached screenshot of about:version. Aldo see a video: https://youtu.be/_weY8GlWXf8

Deleted: Screenshot_20170825-203325.png 286 KB

	Screenshot_20170825-203325.png 286 KB View Download

Ok, finally managed to repro. Looks like an issue specifically in Chrome Beta with Chrome Home (URL bar on the bottom) turned on. It's been fixed in Canary. This is almost certainly fixed by crrev.com/c/560641 which landed the day after 61 branched.

That patch is quite large and M61 is far enough along that I'd be nervous trying to merge it back. Given that Chrome Home isn't shipping by default in 61 (I'm guessing nekr.fabula@ sees it due to a finch trial?) it probably isn't affecting too many users and it isn't really serious.

Given that, I'd say we can probably just live with this in M61 and so there's no action here. Assigning to mdjones@ for more information since I'm not well connected to Chrome Home. Is Home behind a Finch experiment?

For completeness, the original bug that patch was fixing is  issue 711828 

Thanks, I didn't realize Chrome Home was still behind finch.  If we can confirm that Chrome Home isn't going out in M61 stable (beyond possibly a <1% finch trial), then yes I agree we should just call this a dupe of  issue 711828 .

I'm OOO most of next week and M61 is shipping around then. mdjones@, please track this issue in my absence.

We are planning no more than 1% stable on M61; likely less. I don't think we should worry about merging this back since it is a large patch.

Marking WontFix per #7.