Issue 937: Chrome doesn't seem to execute Java menus correctly http://code.google.com/p/chromium/issues/detail?id=937
Comment #27 by artem.ananiev: Deeper investigation shows that AWT bug 6595651 isn't related to this new problem in Chrome. Here is what's going: 1. When a Swing menu is shown, user clicks on some menu item with mouse. 2. Win32 generates WM_MOUSEACTIVATE message for AWT embedded frame (native component, which is a parent of the applet). 3. AWT doesn't handle this message and forward it to DefWindowProc. 4. By default (see MSDN for WM_MOUSEACTIVATE), DefWindowProc sends the same message to all the applet parent components, including JavaPlugin control window and Chrome top-level window. 5. Some time later, AWT embedded frame receives a WM_KILLFOCUS message with an opposite window being Chrome top-level window. The only guess I have is that Chrome handles WM_MOUSEACTIVATE with a call to SetFocus(self) - which looks *wrong* because some component inside the top-level (applet) is already focused. 6. WM_KILLFOCUS is processed by AWT, applet's frame is deactivated and Swing menu is hidden. 7. Win32 sends WM_LBUTTONDOWN/UP messages to applet, which are dispatched to the applet panel instead of [hidden] menu item. 8. No ActionEvents are generated. An option (from AWT side) may be to consume WM_MOUSEACTIVATE events instead of calling to DefWindowProc, if AWT embedded frame is already focused. Still, this looks like a workaround, while a real problem seems to be in Chrome code. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-bugs" group. To post to this group, send email to chromium-bugs@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/chromium-bugs?hl=en -~----------~----~----~----~------~----~------~--~---
