Yes, I've been actively working on a support ticket and simply posting screenshots and tasks of things they are asking me to do. The last post was what we first received prior to any command-line or environmental variable changes.
I heard back from SmartBear Customer care today.
The key was to make sure you have checked "*" from MSAA options
Champion Level 2Hi,
Thank you a lot for the ongoing updates on this case!
I will appreciate it if you provide a bit more details about MSAA approach and provided screenshot:
-- It is my understanding that control recognized by MSAA is web control (<button>?) on the web page rendered by the embedded CEF browser. Is this correct?
-- What type is this test application of? (Native, .Net, WPF .Net , Java, Electron, ...)
-- What version of CEF browser is used?
-- The screenshot does not provide details as for whether the control was recognized as web one or not. Can you please clarify this?
My current guess is that controls are recognized not as web controls, but as some MSAA ones. While this might be fine for you (in case you are creating new test code), my preference is to have controls to be recognized as web ones, so that already existing test code can be used.
