and just for the record, we now have included this chrome bug and solution in a troubleshooting section