I've been working with the IE4 activex control and have had mixed results handling the removal of the window decorations (scrollbars, 3dborders...).
The Driller example program showed me how to extend the undocumented COleControlSite to provide MSHTML the information to NOT include 3dborders and scrollbars on the documents.
This worked fine for my application - but only in a limited way. I have a CView with webbrowser controls - 2 of them. These are constructed at slightly different times and ONLY THE FIRST BROWSER HAS THE SCROLLBARS REMOVED (not yelling, just getting the main point across). The second control does NOT use my extended COleControlSite and the extended function that tells the control to not include scrollbars and 3dborders.
My thoughts lately have been that this might work if I had these controls in a CDialog as opposed to a CView. There seems to be quite a bit of CDialog code dedicated to ole control hosting and I don't think my CView is benefiting from this and might need it. Driller uses a CDialog and I see that as the main difference in our applications (adding another webbrowser control to Driller has positive results).
I'm looking for a comprehensive answer that will hopefully solve my problem and give me more insight as to how the MFC/OLE/ActiveX stuff really works.