{"id":1146,"date":"2010-06-25T12:46:39","date_gmt":"2010-06-25T20:46:39","guid":{"rendered":"http:\/\/blog.mozilla.org\/webdev\/?p=1146"},"modified":"2010-06-25T16:04:08","modified_gmt":"2010-06-26T00:04:08","slug":"flash-updates-in-firefox","status":"publish","type":"post","link":"https:\/\/blog.mozilla.org\/webdev\/2010\/06\/25\/flash-updates-in-firefox\/","title":{"rendered":"Flash Updates in Firefox"},"content":{"rendered":"

This week, Firefox 3.6.4 was released<\/a> with out-of-process plugin support. This means that when plugins crash, it doesn’t take the browser with them.<\/p>\n

But please remember: it’s still important to keep your plugins up-to-date<\/strong>. Out-of-date plugins can be a security risk.<\/p>\n

In a previous blog, I talked about the blocklist service in Firefox<\/a> and its role in keeping users informed and up-to-date with regards to plugins. It looks something like this:<\/p>\n

\"Step<\/a><\/p>\n

As a follow-up to that post, I walked through the update process for Firefox. Here were my testing steps:<\/p>\n

    \n
  1. Edit my blocklist.xml files and preferences<\/a> to blocklist the Flash filename on each platform.<\/li>\n
  2. Restart Firefox<\/li>\n
  3. Visit YouTube (or any page with Flash on it)<\/li>\n
  4. Follow the on-screen prompts until you reach our goal: a browser running an up-to-date version of Flash<\/li>\n<\/ol>\n

    Adobe and Mozilla both need to make this process easier for users. In summary, this is how it went:<\/p>\n