4 ms·
How is bundling flash any different than bundling H.264 in Chrome? none of those are part of the HTML5 specification. And in Chrome, flash is part of the inter
by redial 16y ago
How is bundling flash any different than bundling H.264 in Chrome? none of those are part of the HTML5 specification.
And in Chrome, flash is part of the internal workings. You can't update (or remove) the flash player inside.
- stanleydrew 16y agoI can tell you exactly how, as many others already have in this and other discussions: flash is a plugin; h.264 support is native browser code. Google bundles flash for one reason only: to make sure that users aren't given the chance to shoot themselves in the foot by not upgrading. Everyone downloads the flash plugin because sites require it. It has 98% penetration (perhaps less now with more people using iDevices, but still very high). But people never update the plugin, which is a major security issue. Google has solved that problem in chrome. And you are mistaken that flash is part of the internal workings of chrome. You can disable it: see about:plugins. And there is no need to update it since chrome takes care of that for you.
- antimatter15 16y agoNo. You can disable the internal flash plugin by navigating to about:plugins and hitting disable. It's not part of the internal workings.