Article ID: 266343 - View products that this article applies to.
This article was previously published under Q266343
This article has been archived. It is offered "as is" and will no longer be updated.
Visual C++ developers often use the MSHTML component of Internet Explorer as an HTML parser without a user interface ("UI-less"). If script execution is turned on in this scenario, a number of problems can occur, including frequent host application failures.
MSHTML was never designed to handle this scenario, and Microsoft does not support such usage.
Microsoft recommends that developers always turn off script execution when they use MSHTML in this manner.
Script inside of an HTML page can greatly alter the page's document object model (DOM) through the insertion of nodes into the DOM and the use of such properties as innerHTML and outerHTML. Developers sometimes want to capture these changes by allowing script to execute in their UI-less parsers and trapping any calls made against the DOM.
There is no supported method under any hosting scenario to trap scripting calls against the DOM, other than the events that are generated by the documented DOM and WebBrowser Control event interfaces.
As shown in the WalkAll sample in the Platform SDK, UI-less MSHTML hosts should turn off script execution by responding to the DISPID_AMBIENT_DLCONTROL with the proper response mask. (NOTE: In the code sample below, CApp is the object in the WalkAll sample that contains the MSHTML rendering engine.)
For more information about developing Web-based solutions for Microsoft Internet Explorer, visit the following Microsoft Web sites:
Contact us for more help
Connect with Answer Desk for expert help.