Mozdev.org

I have received many reports that since Firefox 3.6.4, Firefox will hang when opening MS Sharepoint with IE Tab Plus. To fix this, go to about:config in URL then changing " dom.ipc.plugins.enabled" from "false" to "true". Thanks Simon Gaiser for the tip. Also there are many friends mentioned this tip, see BugZilla: https://www.mozdev.org/bugs/show_bug.cgi?id=22754 and https://www.mozdev.org/bugs/show_bug.cgi?id=22948.
An alternative way is just add a setting entry "dom.ipc.plugins.enabled.npcoralietab.dll" and set it to true. It has the same effect as  dom.ipc.plugins.enabled = true.

The former name, "Coral IE Tab", is not very clear and easy to remember. So I decided to change it to "IE Tab Plus", which will clearly show the relationship with the original IE Tab, and is easy to understand. I hope more and more people can get positive perception on this addon.

Since v1.81, the default behavior of popup window in IE engine is popping up a new Firefox window, sometimes with a grayed location bar. However, some people are prefer to use Firefox tabs instead of new windows, and also some other people are prefer to use new IE windows instead of Firefox windows.
So, I provided a new config entry:
Type about:config in Firefox's location bar, press enter, and find coral.ietab.open_newwindow.
The default value is 1, which means, the popup window in IE engine will be a new Firefox window.
If the value is 0, the popup window in IE engine will be a new IE window. This option may also be very useful when Coral IE Tab is not working properly on some IE-only sites, for examples, some OWA sites. But sometimes it will require the users to login again in the newly popped IE window.
If the value is 2, the popup window in IE engine will be always in new Firefox tabs, ignoring the config value of Firefox's browser.link.open_newwindow.restriction setting.
The above config entry will take effect in "Advanced Mode". However, it will be disabled in "Classic Mode", because in design, "Classic Mode" should behave exactly the same as the old IE Tab.

In the beginning, Coral IE Tab's main goal is to switch between IE and Firefox seamlessly. That means, if you have logined in Firefox, you don't have to re-login in IE. This feature is implemented by "cookie synchronization".
 
However, some sites will not only check cookies to verify your login status, but also your browser's user agent string. So, when you switch from Firefox to IE, these sites will find your user agent changed and denies your credential.
 
Back to the Coral IE Tab's main goal, to let you switch between IE and Firefox without re-login, Coral IE Tab will defaultly change IE's user agent to Firefox to make those sites think it is still in Firefox, so everything is switched seamlessly, seams so.
 
But, another problem comes. Some sites will also check browser's user agent and show different contents according to the different browsers. Give IE the HTML for Firefox may make IE display incorrectly. So this is the reason why some sites may not display correctly. "Retry" button in the toolbar at top will temporarily disable this behavior to correct its display.
 
The situation has been changed, when Firefox 3.6 has been released. The old IE Tab is not working in Firefox 3.6 and many old users of IE Tab comes to Coral IE Tab. These people don't concern about the "seamless switching", they just want Coral IE Tab working in the old IE Tab's way. They are confused and complaining about the default behavior.
 
So, I decide to give these people a simpler selection. In v1.80 (will be released soon), users will have to select the "working mode" of Coral IE Tab, if in "Classic Mode", Coral IE Tab will act like the old IE Tab, no cookie sync, no adblock, no user agent problems, everything is just like the old IE Tab. Less powerful, but more stable. If in "Advanced Mode", Coral IE Tab will behave like it used to be.
 
I hope this will make people of both sides happy.