Hello Mathias,
> In fact the plugin uses the old Netscape/Mozilla API for plugins
that is > still used in browser nowadays. As Netscape is a brand name
we decided > to use the name "Mozilla plugin" for that reason. > >
The reason why we didn't do that is simply because the plugin is not >
made for a single browser. In the absence of a product name to use (as
> it indeed can be used in nearly every browser) we took the interface
> (API) name. If we abandoned that I would prefer to name it "browser
> plugin", I don't think that Firefox should be mentioned explicitly.
I agree with this knowledge. > Perhaps we should have a look how
other plugin vendors (like Adobe) are > doing it. A lot of people are
using the Acrobat or Flash plugins, using > a comparable terminology
and description can't be completely wrong.
I think our users are really not that technically minded.
As it works with most browsers, I would call it "browser plugin", as
users generally accept that everything doesn't go with everything.
I would suggest to change the name to "browser plugin", with a note
in the help documentation which browsers are supported.
Thanks a lot Mathias,
Per
