@chaserx,
Thanks for reaching out. This is actually a known issue and has been for a while – I believe it has something to do with the underling Chromium code and what we remove from it. You can view the open issue here:
I’ve added your report in the thread as a +1 on your behalf and will ping the devs to see if we can get an update on the status of the issue.