Everyday Life, Work, Ironman Training

home | photos | toolbox | about me

October 16, 2006

“content parts” of a web browser

Tags: Browser Garage — 12:26 pm Comments (4)


I don’t know if “content parts” is right but wanted to identify what a web browser (or Firefox) handles. Each “part” is distinct and they’re all slightly handled differently in Firefox. There’s opportunity to unify how the different parts are handled or managed, and opportunity to specialize? (optimize) the different parts to take full advantage of why they’re different in the first place.


Web Content
Description: html, rss, images

Web Applications
authentication, account, storage of data,

Examples: E*Trade, Google Calendar, Yahoo!Mail, SmugMug, WordPress

Plug-ins (and Helper Applications)
Description: images, video, sounds, other document formats

Plug-in is “in browser” interaction. Helper application is “outside browser” interaction.

Handled by blah, blah

Examples: Adobe Flash Player, Adobe Acrobat, Java Plug-in, RealPlayer, Windows Media Player, Apple QuickTime


Handled by Add-ons Manager


Opportunities to Unify

Opportunities to Optimize


  1. For optimizing the Web Applications “content part,” see my blog post on The ‘Appify’ Button:

    Comment by Zach Lipton — October 16, 2006 @ 5:52 pm

  2. C’mon now. You should know better, I read your blog.

    Comment by rebron — October 16, 2006 @ 8:19 pm

  3. ewan koh mlay koh ba???

    Comment by princess — June 9, 2011 @ 3:51 am

  4. Yes Princess, we’re related.

    Comment by rebron — June 10, 2011 @ 10:26 am

RSS feed for comments on this post. TrackBack URI

Leave a comment Rafael Ebron's Web site