Sadly, No. And the problem persists into the current Chrome 48.0.2541.0
Servicio de atención al cliente por UserEcho
Sadly, No. And the problem persists into the current Chrome 48.0.2541.0