I can observe the issue, and I’ve verified that the behaviour is different from what we get on chrome on android.
Those differences in UI/UX are very likely a consequence of the UA string.
Interestingly, looking at the logs of the gmail webapp, and more specifically those that indicate that an overridden UA string was sent for a given request, I’m seeing that the first few requests are sent with this UA string:
Mozilla/5.0 (Linux; Ubuntu 14.04 like Android 4.4) AppleWebKit/537.36 Chromium/35.0.1870.2 Mobile Safari
whereas the subsequent requests are sent with this one:
Mozilla/5.0 (Linux; Ubuntu 14.04 like Android 4.4) AppleWebKit/537.36
This looks like a bug in the UA override mechanism. Not sure whether that would fix the floating toolbar issue though, but worth looking into anyway.
I can observe the issue, and I’ve verified that the behaviour is different from what we get on chrome on android.
Those differences in UI/UX are very likely a consequence of the UA string.
Interestingly, looking at the logs of the gmail webapp, and more specifically those that indicate that an overridden UA string was sent for a given request, I’m seeing that the first few requests are sent with this UA string:
Mozilla/5.0 (Linux; Ubuntu 14.04 like Android 4.4) AppleWebKit/537.36 Chromium/ 35.0.1870. 2 Mobile Safari
whereas the subsequent requests are sent with this one:
Mozilla/5.0 (Linux; Ubuntu 14.04 like Android 4.4) AppleWebKit/537.36
This looks like a bug in the UA override mechanism. Not sure whether that would fix the floating toolbar issue though, but worth looking into anyway.