The issue on Chrome's bug tracker [0] that he's linking to appears to return a 403 error. Perhaps they changed their mind on WontFixing it? [0] https://code.go

The issue on Chrome's bug tracker [0] that he's linking to appears to return a 403 error. Perhaps they changed their mind on WontFixing it? [0] https://code.google.com/p/chromium/issues/detail?id=543078 https://code.google.com/p/chromium/issues/detail?id=543078