Pixel 2 on Android 9 and Note 5 on 7.0 same issues.

Tested the issue on android and unable to reproduce this issue

Steps to reproduce:
--------------------------
1. Launched chrome and opened ebay.com
2. scrolled down and observed hide of address bar.

Chrome version:
69.0.3497.100

OS:
Android 9.0 

Android device:
Pixel 2  

@chris: Please check the above steps and let us know if we miss anything. Is this issue consistently reproducible? On which site this issue is seen? Any information on reproducing the issue would help in better triaging.

Thanks!

Does not work on Note 5. Pixel 2 okay.

I think it's related to this bug I reported:

https://bugs.chromium.org/p/chromium/issues/detail?id=873503

Recent tabs are broken. It's like the browser thinks I am a tablet.

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

Yes, I think Chrome thinks the phone is a tablet which is why the address bar doesn't hide.

Testing team, can you please confirm that this is still an issue on a Note 5?

Reporter, is it still an issue for you?

Thanks for diagnosis "It's like the browser thinks I am a tablet."  Hopefully it's been fixed.  If it hasn't, I'll make sure this report gets in the right hands.

This is still happening on my Note 5. This is also happening on my Note 8 now.

Chrome 70.0.3538.80 confirmed on both devices.

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

->tedchoc@ for triage

It isn't being mis-detected as a tablet, but it does think it has an accessibility service enabled.  You likely have some application on your device that is registered as an accessibility service (not flags within Chrome).

This would be under Android Settings -> Accessibility and see what applications are listed there.

We added the ability to turn off the accessibility tab switcher in the later versions of Chrome if you can't uninstall the accessibility service at the Android level (Chrome > Accessibility): https://bugs.chromium.org/p/chromium/issues/detail?id=859401#c15

Marking this as WontFix as I believe all the necessary work-arounds have been landed, but ping this if that isn't the case.

Yep. I use Tasker. So this explains this issue. Although I don't like the approach you have taken with this. How will users know about this new "feature"? Chrome will just behave differently when they has an application turn on accessibility features that could, and more than likely, not related to Chrome in any way. They won't make the connection. Now, when I turn on accessibility, perhaps chrome should say, "Hi! I detected you has accessibility turn on, we are turning on this special recent mode for you, If you want to turn this new mode off, go into advanced settings here and have a box check, "don't warn again". Anyone with accessibility will keep this on and remove the nag box".

Yeah, this was a hard one to fix.  We had to fix it to provide proper accessibility support, and the APIs we had available didn't make it possible to distinguish apps meant to provide assistance to those needing it and apps that are tools built on top of that infrastructure (e.g. tasker).  From the framework side, I think they would see the latter as abusing the API, but I can't fault the apps from taking advantage.

I think your recommendation of notifying users's they are in this state isn't a bad one, but it will be a hard challenge to make that understandable in any amount of short language. 

That's like a reasonable approach to something that is using accessibility unexpectedly. How about if Chrome does an overlay of sorts and says, "accessibility mode detected"? So perhaps a unsuspecting user might connect the dots to how Chrome is all of a suddenly looking totally different? I would not guess this is why Chrome changed nor would I know to look in the settings menu of future chrome to turn this off. At least with this message I would have a clue where to start.

Otherwise I suspect more and more people will reports this as a bug and find out later why this is happening, just like I did.