I see FireFox in your Object Explorer and Chrome.... question... that print popup.... is it coming up when you're printing from Chrome or from FireFox?
Additionally, you mention in another thread that you noticed Chrome is running Chrome 68 and you're running TC 12.42. In that other thread, I recommended upgrading to TC 12.50 to be able to support Chrome 68... is this problem here related to the mismatch of Chrome versions to TC version as mentioned?
Hi Robert!
I thank you for your answer.
I'm currently working only in Google Chrome (GC) because this is the required browser to be used (for testing this project). The popup is different in Firefox (i.e. is more simpler: it just asks me for chossing the printer (please see the atachment)). I think this new type of controls/popup is something created by Google.
Regarding your other question, I can confirm that using GC 64.0.3282.140 (official build 64bits), SmartbearTestExtension12.0.2 and TestComplete 12.42.3048.7 x64, when one wants to print something (i.e. an email from his/hers favourite email web page) some controls appear that are not visible with TestComplete - only some high level controls appear, and I don't know how to deal with its sub-object/children.
Anyway, let's just think there is no incompatibility between GC and TC and return to my initial question: how/where to add this new controls to make them accessible by tests functions? (As an example/similar case (probably) I know that if one finds some weird WPF controls, he/she can add them to the project properties and TestComplete might understand them and it would decompose these controls allowing access to the desired objects/children; I don't know what is the control type/name to add (that's why I've attached some images with some properties in the initial post) and where to place them - this web application is not a WPF one:) )
I thank you once again for your time and support!
R
Hi,
I tried with Chrome and also was not able to get controls from the 'print' overlay to be recognized in TestComplete.
My current understanding is that this is something provided by Chrome itself, implemented as a native binary code and thus not accessible to TestComplete.
The quick idea is to try new OCR functionality in TestComplete 12.6 Beta (https://community.smartbear.com/t5/TestComplete-General-Discussions/TestComplete-Beta-Program-Try-AI-Driven-Visual-Testing/td-p/168632) and check if it works.
