Actually, I'm encountering this issue on Chrome 54.0.2840.98 on Mac too. Did you do some testing or receive some information that indicated that it was Windows only?...