This issue is still happening to me, too. It sounds like it should be a
simple fix from Google but nothing yet. In fact, this never used to be a
problem so what probably happened was that Google rolled out an update
that inadvertently introduced this...