Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

Options for removing the system-wide Flash plug-in Apps
While recent versions of the MacBook Air ship without Adobe Flash installed, the idea of voluntarily removing Flash from /Library/Internet Plug-Ins got some attention when John Gruber wrote about his technique. Put simply, Gruber removed Flash from its default location, thus trying to force sites to load HTML5 versions of content. For instances when that didn't suffice, he would load the page in Google Chrome, a browser which has the Flash plug-in embedded within it. His add-on trick is to enable the Develop menu in Safari and use System Preferences » Keyboard to map a shortcut for taking a page in Safari and opening it in Chrome.

The underlying logic of such an approach is generally twofold. For one, it helps site developers get a sense of how many folks are viewing pages using Flash-free systems, thus possibly encouraging them to publish content that doesn't rely on Flash. Two, and much more pragmatically, it reduces the system load since Flash on the Mac is known to regularly use a large percentage of the CPU, sometimes even after the user has closed the window (or tab) where Flash content was viewed.

Should anyone pursue a route like this, Google Chrome is obviously an option for when content is only available using Flash. I tried that for a while, but for subjective reasons I didn't much like Chrome, mostly because of its lack of support for system-level features (e.g., the built-in pop-up dictionary), large footprint, and auto-updating behavior. So I went hunting for alternatives. Here's what I've found that works:

InDesign CS4: Perhaps earlier versions have it, too, but this version of InDesign has a Flash-embedded version of Opera embedded within it (I recall it was version 9.x of Opera). I can't speak to the current version of InDesign, now at 5.5, but standalone version 5 does not have Opera. Perhaps it's only installed when a full Creative Suite installation is performed.

OmniWeb (currently v. 5.10.3): Right clicking on this application and choosing Show Package Contents will reveal a PlugIns folder. Simply move or copy the Flash plug-in here (even the one embedded in Chrome) and this browser will handle Flash content.

iCab (currently v. 4.8): This is my personal preference. It has the leanest footprint of the options I've found, and it easily imports (or just uses) things like Bookmarks, History and Cookies from Safari. While it doesn't have a Plugins folder embedded within it, simply creating one called PlugIns with a copy of the Flash plug-in will work.

Perhaps there are other browsers which can be used, but my tests with SeaMonkey, Camino, Firefox, Shiira, Sunrise, and the current Opera (v 11.10) were not successful.

[crarko adds: I tested this on a few of the mentioned browsers, and it works as described.]
    •    
  • Currently 4.17 / 5
  You rated: 1 / 5 (6 votes cast)
 
[9,486 views]  

Options for removing the system-wide Flash plug-in | 4 comments | Create New Account
Click here to return to the 'Options for removing the system-wide Flash plug-in ' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Re: Options for removing the system-wide Flash plug-in
Authored by: Uncle Asad on May 11, '11 01:43:46PM

For Camino, you’d install the Flash plug-in inside Camino.app/Contents/MacOS/plugins instead.

Hacking an application bundle is never a very good idea, though, so the forthcoming version of Camino will support loading plug-ins from an Internet Plug-Ins folder inside of the ~/Library/Application Support/Camino folder.



[ Reply to This | # ]
Re: Options for removing the system-wide Flash plug-in
Authored by: NaOH-Lye on May 11, '11 04:32:02PM
Ah, I'd tried installing Flash into Camino.app/Contents/Plugins. Thanks for pointing out what will work. And good to know about the future Camino design plans. I had no idea.

[ Reply to This | # ]
Flushing Flash is tricky
Authored by: WaltFrench on May 11, '11 05:35:47PM

Yes, Chrome embeds Flash and does not use the plugin that Gruber advised how to remove. Many other browsers also use Flash from its default location and so won't show Flash, either.

Before removing Flash, I could watch the Flash plugin grow its RAM footprint every time I opened and closed a page that had a Flash ad or whatever. Eventually, Safari, and all the open windows that I load up before getting onto a plane, would crash, and I would go unproductive until I could reload my last pages.

However, it's not all smooth sailing. While Safari has not crashed on me once, Chrome DID crash my whole system not that long ago. In my case, opening a couple of videos and then selecting the window with Exposé, predictably triggers the hard crash after visual artifacts.

This is your typical Google “beta” software with alpha-quality bugs.



[ Reply to This | # ]
Options for removing the system-wide Flash plug-in
Authored by: NaOH-Lye on May 13, '11 02:38:36PM
Since SeaMonkey is a Gecko-based browser like Camino, the method Uncle Asad described up above can also be used in SeaMonkey. A plugins folder doesn't exist by default, but creating one in the same location as Uncle Asad described for Camino will work.

[ Reply to This | # ]