Issue 2673: Flash: IME not available http://code.google.com/p/chromium/issues/detail?id=2673
Comment #5 by [EMAIL PROTECTED]: I noticed this issue consisted of two technical issues listed below. 1.A plug-in process does not have top-level windows. As far as I have investigated, when a process creates a top-level window, Windows starts an IME (i.e. loads IME DLLs and attaches them to the process) and attaches its message hooks only to the top-level windows of the process. That is, a window which needs IMEs must be a child window of the top-level windows of its owner process. On the other hand, when Chrome starts a windowed plug-in, a plug-in process creates child windows and set their owners to ones created by a browser process. This implementation prevents Windows from attaching IMEs to a windowed plug-in. To fix this problem, we need to create a top-level window for each plug-in process. Nevertheless, this change causes some rendering problems, e.g. clipping, changing coordination from absolute one to one relative to the owner window, etc. 2.A plug-in process does not dispatch Windows messages to the DefWindowProc() function. An IME needs its owner process to call the DefWindowProc() function and dispatch window messages used by the IME to its hook functions. Somehow, the CallWindowProc() function does not dispatch the input window messages when its message proc is a handle to the DefWindowProc() function. This prevents a plug-in process from dispatching IME-related window message to the hook functions. To fix this problem, we need to create a wrapper function which encapsulates the DefWindowProc() function. We need to talk with those who implemented this plug-in code to identify the best implementation to fix this problem. -- 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 [email protected] 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 -~----------~----~----~----~------~----~------~--~---
