I have worked with Microsoft WebBrowser control, MSHTML (the HTML parsing and rendering engine behind the WebBrowser control) and Internet Explorer quite a bit, and I have gained a lot of experience and information about them.  I have several articles on this subject, each of which cover a certain point about the topics mentioned above.  Here is a list of articles on this subject; I will update this list as I add newer articles.  Some of the articles on this list you may already have seen, the others are new.  I have also provided a short description on what each article is about.  Hope they will be useful to you.

Almost everyone has used the MFC AppWizard to create a CHtmlView-based application at least once.  Many of us also have written programs which are totally based upon CHtmlView and hence on the WebBrowser control.  When you use the MFC AppWizard to create the project, you'll get a relatively nice and functional web browser right away.  You can simply implement standard commands of a web browser like Back, Forward, Home, Refresh, etc.

The WebBrowser control (and CHtmlView, as its wrapper) is a great tool.  It saves you quite a bit of work to enable web-browsing features inside your applications.  But since it's not written by you, you have a limited amount of control over how it looks and acts.  The developers of WebBrowser control and MSHTML have provided use some advanced hosting features, so that once an application implements them, it can customize the behavior of the WebBrowser control in more aspects.  These customizations are accomplished by a set of interfaces.  The host application has to implement these interfaces, and MSHTML will query its host for these interfaces, and uses them if available.  These interfaces are IDocHostUIHandler, IDocHostShowUI, and ICustomDoc, w

The WebBrowser control stores many kinds of different information about user preferences inside the registry.  These settings are stores in the HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\ registry key (as well as the keys below it).  Investigate that registry key using REGEDIT.EXE.  You'll find many different settings there.  Changing those settings will change how the WebBrowser looks and acts.  See my Changing IE Show Picture Setting article for an example of how to change a key value that toggles the "Show Picture" setting of the WebBrowser control.  What is important is touching any keys or values at that location will affect all the instances of the WebBrow

In my Advanced CHtmlView Hosting article, I showed a way to disable the context menu for the WebBrowser control.  Inside the ShowContextMenu( ) handler, you can display your own context menu using ::TrackPopupMenu( ).  This requires building your own menu using the Win32 API, or creating a menu resource, and loading it.  However, there are disadvantages in this approach.  First of all, you have to implement the functionality of every menu item yourself, which could be a tedious task.  Other than it, maybe you only want to disable one item of the context menu, and show the rest.  Of course you might say that one can create a menu resource that has all the items as the WebBrowser's default c