Their response seems to suggest they may not have fully understood your request. We are not "making components" that are supposedly compatible with Firefox.
To understand why this is a much more difficult situation than it might appear to be, you need to understand some of the technical issues plus a bit about the history of Firefox.
Once upon a time, there was a browser called Mozilla but the guys writing eventually made it into not just a browser but a fully-fledged application suite. Some people felt that it was getting too bloated and formed a break-away project to extract the browser and develop it as a light-weight, stand-alone program. This eventually became what we know as Firefox.
Internet Explorer comes in two bits, a core component called MSHTML that draws web pages, and some stuff that adds extra features on top of just displaying web pages e.g. plugins, zone security, etc. MSHTML has been designed so that it can be used by *any* program (not just IE) that needs to show web pages e.g. Awasu.
There was a lot of demand for the Mozilla team to provide a drop-in replacement for MSHTML i.e. a component that people could use instead of MSHTML. It would work in exactly the same way as MSHTML except that it would use Mozilla's web page-drawing component (called Gecko) instead of MSHTML. The Mozilla team never did this but somebody else did
. Note that this is *not* an official Mozilla project, it's just something somebody has done in their own time because there was a need for it and they wanted to fill that need.
The problem is this: the Firefox team took the old Gecko browser code from Mozilla and worked on it independently so now their browser component is not the same as Mozilla's. Awasu uses the Mozilla-based browser component which doesn't know anything about Firefox. There is a comment on the Mozilla ActiveX Project's web site
that says <i>Future versions of the control are likely to be built using the Firefox source branch (April 10 2005)</i>. What's happening with this is anyone's guess.
<b>The bottom line is this: Unless the Firefox team provide an MSHTML-compatible browser component <u>that other programs can use</u>, neither we nor anyone else will be able to show web pages in a way that will recognize Firefox plugins. </b>
I also use Firefox as my default browser and there's nothing I would love to do more than to get Awasu to use Firefox but until they provide such a component, there's nothing we can do. Believe me, it's not just Awasu that has this problem! There are lots of other programs that show web pages that also want to use Firefox but can't because this component is not available.
Incidentally, all of this explains why Awasu cannot use Opera as its embedded browser - they don't provide a MSHTML-compatible browser component that can be used by other applications.