I am seeing the same issue in my app on 26.1. I didn't see this on earlier versions. I will try to test on 26.2 beta.