What's newsworthy about this? It seems like this is a bug in Chrome 56, the current beta version (not stable), in a non-default configuration (the built-in PDF plugin disabled), and the Chrome team is treating it as a bug because it's been assigned to someone to work on. What am I missing?