Sadly, No. And the problem persists into the current Chrome 48.0.2541.0
Service d'assistance aux clients par UserEcho
Sadly, No. And the problem persists into the current Chrome 48.0.2541.0