Re: Response to WM_GETOBJECT or getting control's properties is too slow on Vista and Windows 7

On júl. 27, 09:47, Alexander Surkov <[email protected]>
wrote:
> On Jul 26, 11:11 pm, ceex <[email protected]> wrote:
>
>
>
>
>
> > Hi,
>
> > I am a QA engineer and I got to automate a plug-in of our product
> > which, of course, is embedded into a web page and could be used in
> > both IE and FF. For this I use Microsoft UI Automation (http://
> > msdn.microsoft.com/en-us/library/ms753388.aspx) framework which is
> > working fine in both browsers on Windows XP. However, the problem is
> > that the same version of FireFox on Vista and Windows 7 behaves a
> > little bit differently at least I suspect this. What I have been able
> > to figure out so far is that when the framework tries to map the
> > structure of the tested application (component) it sends WM_GETOBJET
> > message(s) and uses the returned pointer to get information about the
> > controls of the application (component). The problem is that the
> > tested application`s (component) answer to the message or later
> > getting the properties is extremely slow and makes it impossible to
> > use. The situation is the same when a web page`s structure is being
> > mapped.
>
> > Environment in which I tried to automate my application:
> > -Vista 32 Enterprise SP1 Eng and Windows 7 RC
> > -.NET 3.5 SP1
> > - FireFox 3.5.1 and the latest build from here:http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-trunk/
>
> > Has anybody ever come across this slowness of Firefox accessibility?
>
> > Thank you in advance!
>
> > Regards,
>
> > Zoltan Logo
>
> Hi. Firefox doesn't support UI Automation afaik. It exposes MSAA only,
> WM_GETOBJECT is handled as a part of MSAA implementation. Probably UIA
> calls are processed somehow to allow work with MSAA servers and
> therefore you can work with Firefox via UIA interfaces. Possibly
> Windows XP and Vista have different implementation of this.
>
> Alex.- Idézett szöveg elrejtése -
>
> - Idézett szöveg megjelenítése -

Hi,

Thank you for your answer! Eventually I could solve the problem
without knowing exactly what caused it. The solution was to write my
own client side custom providers for the following classes:

- MozillaUIWindowClass
- MozillaWindowClass
- MozillaContentWindowClass

Regards,

Zoltan