On Windows, some shortcut key events are not being passed to plug-ins. For example:
Our plug-in is a WYSIWYG editor and these shortcut keys are very important to the functionality of our software.
Our Windows plug-in can be downloaded from:
Test page to load the plug-in is here:
Vlad, could you specify the exact steps to download and install the plug-in for Safari 3.0 on Windows? Thanks!
> could you specify the exact steps to download and install the plug-in for
> Safari 3.0 on Windows?
I have just downloaded the dll to C:\Program Files\Mozilla Firefox\plugins and restarted Safari.
Sorry, NPXStandard.dll should be in:
I have this same problem on Windows. Short cut key events that are defined by the browser are not passed to any script.
Turns out that this problem is mostly in Safari, not WebKit. Closing as INVALID, as it will be tracked in Radar.
Thank you for reporting this!
Actually, I'd like to keep this open to simplify communication, sorry for the noise!
Does this plug-in work in Internet Explorer? I've tried copying it to C:\Program Files\Internet Explorer\Plugins, but the test page still doesn't load it. Is there anything else I should do to see it in action in IE?
In Firefox, I'm seeing that the plug-in consumes all Ctrl-key shortcuts, even those it doesn't handle. This doesn't look like ideal behavior, so I'm wondering about IE.
>Does this plug-in work in Internet Explorer?
Yes. Open a command prompt and cd to the location of NPXStandard.dll. Then type:
I've been looking at what messages get delivered to the XStandard plug-in window in IE and in Safari, but I do not see any difference. In both cases, the window gets the appropriate WM_KEYDOWN and WM_KEYUP messages (Firefox also sends WM_CHAR, but that shouldn't affect accelerator processing). I'm using Winspector Spy <www.windows-spy.com> to trace Windows messages.
Notably, the windows are named differently in the two browsers: Afx5d50000:100b "xeditor" in Safari, and Afx10000000:100b "XStandard XHTML Editor" in IE. This makes me wonder if different code paths are used for event processing.
Given that the behavior of IE and Safari looks identical when using the tools I have, it seems that I need more information about inner workings of the plugin. Could you please describe how it handles keyboard input (possibly via e-mail)?