Sadly, No. And the problem persists into the current Chrome 48.0.2541.0
Customer support service by UserEcho
Sadly, No. And the problem persists into the current Chrome 48.0.2541.0