We have a problem. After a long delay, we finally upgraded to the latest patch to be ready for the new daylight savings time, we cannot use OWA for email on a custom browser that is a container app for IWebBrowser2 interface. The problem is that when a new message is created, the enter key doesn't work. When I looked at the problem in the debugger (and through Spy++'s message tracing), I learned that new scripts for new message window from OWA somehow causes the WM_KEYDOWN message on enter key to trigger WM_COMMAND message rather than sending a subsequent WM_CHAR message. Has anyone ever experienced this problem? The older version of Exchange severver used IE5 version of the script, and the new patch made the OWA to send IE6 version of the script. Any help in this regard is much appreciated.
