Article ID: 926047
Important This article contains information about how to modify the registry. Make sure that you back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/322756/ )How to back up and restore the registry in Windows
The AutoComplete box in an iframe object may not appear in the correct location in Microsoft Internet Explorer 6.
In some cases, this problem occurs because the window.screenTop property value is calculated incorrectly. In other case, if the iframe object has a relative position style, the offset of the iframe object is incorrect when it is used to calculate the position of the AutoComplete box.
Hotfix informationA supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=supportNote The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
PrerequisitesYou must have Microsoft Windows XP Service Pack 2 (SP2) installed to apply this hotfix.
Restart requirementYou must restart the computer after you apply this hotfix.
Hotfix replacement informationThis hotfix replaces the hotfix that is described in Microsoft Knowledge Base article 920681.
Registry informationWarning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
After you apply this hotfix, you must add and configure a registry value. To do this, follow these steps:
File informationThe English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
Windows XP with Service Pack 2 (SP2), x86-based versions
Collapse this tableExpand this table
Windows Server 2003
Service pack informationTo resolve this problem, obtain the latest service pack for Windows Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/889100/ )How to obtain the latest service pack for Windows Server 2003
Hotfix informationTo resolve this problem in Microsoft Windows Server 2003, apply the hotfix that is described in the following Microsoft Knowledge Base (KB) article:
(http://support.microsoft.com/kb/931306/ )FIX: The AutoComplete box in an iframe object may not appear in the correct location in Internet Explorer 6
Microsoft has confirmed that this is a problem in Microsoft Internet Explorer 6. This problem was first corrected in Windows Server 2003 Service Pack 2.
Steps to reproduce the problem