Please support Chrome V107

Anyone know when Edge/Chromium 108 will be supported? We can't control browser versions in our org and TC only supporting up to 105 is really impacting us

Thanks Kitt. There are lots of good stuff in your response that are valuable to us plus others. I'll make sure to refer to this discussion during our next enterprise upgrade. Thank You for taking the efforts.

I'll share some thoughts on this that may help others experiencing similar issues. We have been running on the latest version of Chrome (now on v108) without issue for about 1.5 years - always several versions ahead of the TC "supported version". The only time we have had issues with the webdriver (IE: the TC Browser Extension) it has usually been after an TC/TE upgrade or GPUpdate.

My first suggestion, would be to open Object Browser or Object Spy tool in TestComplete and see how TC see's the pop-up - occasionally TC may view this object (ex: iframe) as being on another page or not having to proper permissions to access. The simple solution being to add a line in TC to switch the page/window it's looking in or set the Browser run permissions (see community post here and here). 

If that doesn't solve your issue, I would suggest looking on your machine to see if there are any outdated references to older versions of TestComplete, TestExecute, and the TestComplete Extension that may cause issues.

If you are having upgrade issues - look for old references to TC 14 or TELite in Services, RegEdit, Local/AppData, Program Files, etc. (and remove them - this may require a fresh install/setup of TC)

If you still have issues accessing objects or if the browser is listed as a "Process" instead of a "Browser" in the TC Object Browser - this usually points to TestComplete Extension being the culprit. Update or reinstall the extension and insure everything is correctly configured on your system:

For those in larger Enterprise systems that have global policies managed and updated by an enterprise admin - it can be difficult to avoid the onslaught of the Chrome Auto-Updater (you have to change registry keys, delete local app data, stop some Chrome services, config default browser settings, etc). Here are a few things to check to insure your browser Auto-Update is disabled - if indeed you are required to run on an older browser version:

**insure any browser changes you make (turn auto-fill off, enable js and pop-ups, etc.) are not being save under a different profile (ex: 'Profile3') in your local Chrome AppData folder.

These suggestions may not work for everyone, but they have proven to be helpful on several occasions when the web driver and/or TC isn't playing nice. Hope this may help others with similar issues.

tjohn The last one on that page is Chrome 103 so that one should work.

Thanks Marsha_R. In your opinion, what would be considered as a safe(st) version of chrome to use with v15.46 of TestComplete in regards to PopUps.

tjohn it's the Chrome version that's affecting the popups. Here's where you check for that

https://support.smartbear.com/testcomplete/docs/app-testing/web/general/supported-browsers-and-technologies.html

Oh my!! @thanks for this heads up abadamo. We are currently on v15.40 and planning to upgrade to v15.46 in 2 weeks. This forewarning helped greatly.

Would you be able to share the last version number of TestComplete wherein the interaction with popups were stable..

Yeah we have been having this issue as well for almost a month. Its a huge blocker for us. The latest update (15.46) does not fix the issue

Thanks rpfaucher1 for this bulldozer approach (lol) that works for your scenario and hopefully  some other too. 

But, in our case, we have to verify the presence of the pop up window, and certain contents within the pop up windows - which make it imperative that TestComplete interacts with the pops ups. This makes it harder for us since we cannot bypass the pop up windows. So hopefully TestComplete adds Pop-Up handling as part of their release regression testing strategy and ensures full compatibility.