Same behavior in chrome on win server 2016 datacenter, which means it's probably broken in win 10 too