On Wed, Jan 19, 2011 at 1:05 PM, Jacek Caban jacek@codeweavers.com wrote:
On 1/18/11 7:31 PM, Erich Hoover wrote:
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):
Hmm, it means that another run of tests (at least required subset of existing test_WebBrowser) with client's IOleCommandTarget disabled would be interesting. Do you feel like writing it? Otherwise we'd need at least a FIXME in this case.
I've been working on putting such a test together, I actually just finished it up when I got your message. It's attached to this email, and I would appreciate it if you would take a look - it ends up being rather non-trivial since native caches the IOleCommandTarget on creation of the container.
Corresponding test results: https://testbot.winehq.org/JobDetails.pl?Key=8449
Erich Hoover ehoover@mines.edu