Comment #18 on issue 20717 by [email protected]: Plugin custom cursors are not supported. http://code.google.com/p/chromium/issues/detail?id=20717
Not sure what the right flow is here. On Windows, they patch SetCursor and stash away the set cursor in current_windowless_cursor_. Then, when WebPluginContainerImpl::handleMouseEvent gets called, it calls WebPluginDelegateImpl::HandleInputEvent which passes the stored cursor up, and then it's sent to ChromeClientImpl::setCursorForPlugin. On the Mac, interposition doesn't talk to webkit/glue; it directly fires off IPCs to the PluginProcessHost. And in fact, the interposer lives in chrome/, which is a layer above glue. Ugh. -- 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 -- Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs
