QT on Windows is horrible, but disabling it outright and requiring users to start Chrome with a custom commandline, without warning and after an automatic (and hidden) update? Let's just say it did not go down well at work, where we use Chrome and QT for inhouse enterprise applications. I understand the need to push the envelope on web standards and that needs to happen at a rapid pace, but at least give us enterprise developers a chance to override it. Enterprises do not develop software at breakneck speed Google, it's just not worth it.
It handles QuickTime and Java the same way it handles Popups. It puts a yellow bar at the top asking for permission to "Run this time" or "Always run on this site".
Hit the "Always run on this site" button on Apple.com and your internal sites.
It's now "ask for permission to run" instead of "always run". It's in the same boat as intranet sites needing popup permissions.
Chrome clearly isn't made for the enterprise. IE has historically been a poor browser, but it gives sys admins quite a bit of control over how and when updates are applied.
I think the myth isn't that Chrome and Firefox don't offer enough control, but that such control is actually necessary. I suspect it is possible to build enterprisey systems that are robust enough to handle automatic browser updates.
