Comment by becarefulyo

I think you're right, looks like it was only fixed for Edge.

Discussion of technical challenge is here: https://blogs.msdn.microsoft.com/oldnewthing/20150129-00/?p=...