If it doesn't, I'd recommend that you reach out to the appropriate support channel for your Chromebook. Just click on "Check for Update" and see if it updates. If you go to chrome://components, you might be able to force the update. We're on a monthly release cycle, so we're already halfway through the release.
Updates on Chrome are rolled out gradually across the population, which helps to soften the network impact of the entire Chrome user-base downloading an update simultaneously, but even then, I'd expect you to have received it at this point. It's a long-term win, but as we can attest to ourselves, writing installers for a large population means that anything that possibly can go wrong, will go wrong, given a population at Flash Player or Chrome scales. The transition has not been perfect, and they're still continuing to identify issues and resolve them. Chrome actually has two different updaters inside of it, and they've been working to use the Component Updater for Flash updates, because it solves a number of load and logistics problems. There's also a presentation that clarifies what the experience will look like moving forward:įlash Player is a built-in component of Chrome (including Chrome on ChromeOS), and under normal circumstances, would stay synced with the browser. (1) Where aggregate usage of a specific domain puts it in the top 10 domains using Flash, based on Chrome’s internal metrics. This whitelist will expire after one year, and will be periodically revisited throughout the year, to remove sites whose usage no longer warrants an exception.Ĭhrome will also be adding policy controls so that enterprises will be able to select the appropriate experience for their users, which will include the ability to completely disable the feature. To reduce the initial user impact, and avoid over-prompting, Chrome will introduce this feature with a temporary whitelist of the current top Flash sites(1). We will continue to ship Flash Player with Chrome, and if a site truly requires Flash, a prompt will appear at the top of the page when the user first visits that site, giving them the option of allowing it to run for that site (see the proposal for the mock-ups). If a site offers an HTML5 experience, this change will make that the primary experience.
Later this year we plan to change how Chromium hints to websites about the presence of Flash Player, by changing the default response of ugins and Navigator.mimeTypes. We will continue to work closely with Adobe and other browser vendors to keep moving the web platform forward, in particular paying close attention to web gaming. This change reflects the maturity of HTML5 and its ability to deliver an excellent user experience. While Flash historically has been critical for rich media on the web, today in many cases HTML5 provides a more integrated media experience with faster load times and lower power consumption. Navigator.Plugins() and Navigator.MimeTypes() will only report the presence of Flash Player if the user has indicated that the domain should execute Flash, or if the site is in one of the Top 10 domains using Flash. !searchin/chromium-dev/HTML5$20by$20default/chromium. I'd highly recommend that you read the actual authoritative statement from Google. Unfortunately, bloggers don't necessarily hold themselves to the highest journalistic standards, especially in a world where headline click-throughs are what pays the bills, not quality reporting.