I've been watching another thread where this issue was first reported.
While I appreciate someone taking time to provide a workaround, it does
not excuse Google still not actually fixing the issue. I have seen it
too often that Devs provide 'new and ...