BUG: Errors Occur When Window.Open Is Called in InfoViewer (175260)



The information in this article applies to:

  • Microsoft Visual InterDev 1.0

This article was previously published under Q175260

SYMPTOMS

When using the InfoViewer to browse a page that contains a "Window.Open," a new instance of the browser appears along with one of the following error messages:
Microsoft JScript runtime error
[Line: xx] Invalid procedure call or argument"

-or-

Microsoft VBScript runtime error
[Line: xx] Object doesn't support this property or method: 'open'"
NOTE: The Window.Open works as expected in Internet Explorer.

CAUSE

The conditions that cause this behavior are as follows:
  • Client Side Script using the "Window.Open" command.
  • Browsing within the InfoViewer.
InfoViewer is not capable of properly starting a new instance of itself from within the Visual Studio shell.

RESOLUTION

Use Internet Explorer to view the pages that calls the "window.open" method.

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. We are researching this bug and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

Steps to Reproduce Behavior

  1. Add a new .htm file to an existing Visual InterDev project. Name the file "default1.htm."
  2. Copy the following code and paste it into the file created in the previous step:
          <INPUT TYPE="button" NAME="Button1" VALUE="Open other Window"
            onClick="window.open('default1.htm', 'window',
            'scrollbars=yes,status=0,resize=0,width=625,height=369')">
    					
  3. Save the file.
  4. Preview the above file in the InfoViewer. If you don't have "InfoViewer" set as your default browser within Visual InterDev, right-click the file in the "FileView" pane and choose "Browse With," then "InfoViewer" from the Shortcut menu.

REFERENCES

For the latest Knowledge Base articles and other support information on Visual InterDev and Active Server Pages, see the following page on the Microsoft Technical Support site:

Modification Type:MajorLast Reviewed:5/2/2006
Keywords:kbBug kbide KB175260