Article ID: 946102 - View products that this article applies to.
Consider the following scenario. In a .NET Framework 2.0-based application, you use a System.Windows.Forms.WebBrowser control to host Web pages. An ActiveX control is on the Web page. In this scenario, the ActiveX control will not receive keyboard navigation events. For example, if there is a ListBox control on the Web page, you will be unable to switch among the list items by using the UP arrow key and the DOWN arrow key.
Hotfix informationA supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next .NET Framework 2.0 service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
PrerequisitesTo apply this hotfix, you must have the .NET Framework 2.0 Service Pack 1 (SP1) installed.
Restart requirementYou must restart the computer after you apply this hotfix.
Hotfix replacement informationThis hotfix does not replace a previously released hotfix.
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.
Collapse this tableExpand this table
This problem does not affect the AxWebBrowser ActiveX control. This problem occurs only with managed WebBrowser controls.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.