@migueldeicaza @samsaffron that's Chrome/Win's problem though. They need to fix it, have been nagging about this for over a year now