firefox - Exact difference between add-ons, plugins and extensions -
what exact difference between plugins, add-on , extensions. have read lot , confused, example see these 4 definitions:
1-fire-fox says "add-ons collective name extensions, themes , plugins" (see https://support.mozilla.org/en-us/questions/790919)
2-www.differencebetween.net says "plug-in , add-on extensions ... plug-in term used when referring third party software (interact program) flash player ...
3- wikipedia (https://en.wikipedia.org/wiki/plug-in_%28computing%29) says plugin being deprecated.
4-i have read in website plugins larger add-ons , consist add-on concept.
also have read answer provided in firefox add-on vs. extensions vs. plugins , http://colonelpanic.net/2010/08/browser-plugins-vs-extensions-the-difference/
however want understand these differences in firebreath plugins execute automatically through user's consent , add-on should install manually. think plugin embed in htm page while add-on in form of separated file xpi in fire-fox.
any exact, comprehensive , precise definitions these 3 concepts emerge differences appreciated.
general rule of thumb:
plugins
when you're talking web browser, plugin talks npapi or similar plugin, specific page. ie doesn't support "plugins" per se, have activex controls can fill similar function, though there bho (browser helper object) activex controls more similar extensions. (the firebreath team) use term "plugin" refer works npapi plugin , term "extension" refer works typical extension (firefox xpi, chrome crx, etc).
plugins know page in; don't know else browser or loaded in other pages.
plugins have been responsible lot of security problems, since run native code. has led lot of discrimination against them -- of deserved. because of this, , because npapi royal pain in neck (hence firebreath created), browsers trying phase out plugins. plugins should never used unless there no other way solve problem.
that said, there lot of cases option.
extensions
an extension specific browser, , bit different on each browser, tend able learn more overall state of browser; may automatically added pages, accessible separately page, etc.
add-ons
add-on more of generic term used mean lot of different things. means depends on talking, mozilla definition any; adds functionality web browser, regardless of context.
key differences
extensions tend automatic once installed. plugins instantiated in 1 of 2 ways: 1) <object> or <embed> tag in html of web page, or 2) because registered handler mimetype browser doesn't support.
firebreath
firebreath deals plugins. has nothing typical browser extensions, plugins. c++ framework, not javascript framework, , allows add functionality can used within web page. typically firebreath plugins used inside <object> tag.
firebreath post-npapi
as may or may not know, chrome has dropped support npapi plugins (as of version 45) , firefox has done of version 52 (excluding version 52 extended support release, support them year). firebreath 2.0 being used in production several companies , can produce "plugins" (not plugins, work similarly) can work google chrome , firefox via native messaging via helper extension. main limitation drawing; there no way draw directly browser across native messaging (well, no way, , no way @ on platforms other windows).
eventually may add support abstraction draw using canvas / webgl on native messaging bridge in firebreath 2.0, hasn't been done yet. frankly, don't need it, haven't bothered it. firebreath open source framework has unfortunately not received enough support users in last couple of years , documentation bit outdated , there lot of little things haven't been done.
the native messaging method relies on extension -- did confuse everyone, of course, because way allow communicate firebreath plugins page in google chrome or firefox.
*(last updated mar 6, 2017; firefox 52 scheduled release tomorrow)
hope helps. see also:
Comments
Post a Comment