[PATCH 2/4] shdocvw: Implement IWebBrowser_ExecWB.

Erich Hoover ehoover at mines.edu
Tue Jan 18 12:31:33 CST 2011

On Tue, Jan 18, 2011 at 3:08 AM, Jacek Caban <jacek at codeweavers.com> wrote:

> ...
> I'm not sure what you mean by "hijack the IOleCommandTarget". All we do is
> implementing client's IOleCommandTarget. It's something different from
> document's one.

I understand that, but apparently the native implementation (testing on the
test bot WXPPROSP3) sends the command to the client IOleCommandTarget
instead of the document IOleCommandTarget (at least under the conditions of
the webbrowser tests).  That is what I mean by hijacking, the command is
going to the "wrong" target.  My guess would be that there is some sort of
priority mechanism, though I have no idea how it would work (except maybe
"if there's a client/container then send to that target, else send to the
document target).  I've attached a test where I disabled the
client/container, and you can see that it then gets passed through
(QueryStatusWB will return success instead of passing through the client
target and returning failure):

Erich Hoover
ehoover at mines.edu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.winehq.org/pipermail/wine-devel/attachments/20110118/1b561955/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: QueryStatusTest.diff
Type: text/x-patch
Size: 2975 bytes
Desc: not available
URL: <http://www.winehq.org/pipermail/wine-devel/attachments/20110118/1b561955/attachment.bin>

More information about the wine-devel mailing list