When you try to view a Web page that contains IFRAME elements in Microsoft Internet Explorer, you receive the following script error message in Microsoft Internet Explorer:
Object does not support this property or method
If a Web page contains an IFRAME element and if an
src attribute points to a Scalable Vector Graphics (SVG) file (.svg), the
OnLoad event of the IFRAME element occurs before the
OnLoad event of the .svg file. If the Web page tries to access the .svg file when the IFRAME
OnLoad event occurs, you receive the error message that is mentioned in the "Symptoms" section.
A Web page that contains an IFRAME element and an
src attribute that points directly to an .svg file is known as a "full-page embed." When you use a full-page embed to host an .svg file, it is the same as if you typed the URL for the .svg file in the address bar in Internet Explorer.
Microsoft Knowledge Base articles 912945 and 912812 describe recent ActiveX Control implementation changes. An external script is now used to create a Web page for a full-page ActiveX control. Therefore, use of the ActiveX control does not require activation. However, this implementation change modifies the order of events. The
OnLoad event of the IFRAME element now occurs before the
OnLoad event of the .svg file.
To work around this issue, use one of the following methods:
- Make sure that the Web page does not access the .svg file in the OnLoad event handler of the IFRAME element. Instead, make sure that the .svg file is accessed only after it is initialized in its OnLoad event.
- Use an external script to embed the .svg file directly on the top-level page. For more information about how to embed objects by using external script files, visit the following Microsoft Web site:
- Make the IFRAME element point to an intermediate HTML page that embeds the .svg file. To do this, you may have to use an external script file to embed the .svg file on the intermediate page. If you do this, the ActiveX control does not require activation.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.