It's a Chromium issue as far as I know and it's already fixed in latest developer version so I guess it's a matter of time for the fix to reach stable channel.