Chrome pop ups in an AUT, you know a few things about it:

To handle the pop up:

1. Please use this line in your script:

**Browser(''micclass:=Browser'').HandleDialog micOK**

2. Please don't start the run when there is a pop-up in Chrome.

When there is a pop-up in Chrome, we cannot set up the state in our agent correctly due to Chrome restrict under such state, Chrome will block the communication between the page and the extension, and eventually our agent won't be in good shape.

If the OK button in the pop up is freezing the machine when is spied, is because these pop ups in Chrome are not supported.Similar technical reason that Chrome block some communications.

More information please see HPE online help :

https://admhelp.microfocus.com/uft/en/14.03/UFT_Help/Content/Addins_Guide/Chrome_Limitations.htm

Hi @bhogapuram,

According to Micro Focus Document [KM00494510][1], there is a known issue with UFT recognizing popup objects in Chrome. The listed solutions are as follows:

Currently, in order to click in the dialog popup in Chrome, user needs to use the below work arounds:

1. SendKeys - To press the OK button always selected by default in the Pop-up wait 2

Set obj = CreateObject(''WScript.Shell'') ' Creates object we can use to call SendKeys

obj.SendKeys ''{ENTER}''

Set obj = Nothing ' destroys object (no longer needed once typing is done)

2. Recording on the dialog with no add-ins

a. Load QTP/UFT with no add-ins

b. record the click operation

c. Load QTP/UFT with web add-in

d. Set the relative coordinates for the buttons in the dialog box to press:

Window(''Browser'').Window(''mywindow'').click 290,83

Note: Ensure that both windows has the require object properties to be identify in chrome (change between chrome and IE)

.3. Low Level Recording.

.4. Insight Feature (Image based testing) - Only for UFT 11.5x and later

[1]: https://softwaresupport.softwaregrp.com/group/softwaresupport/search-result/-/facetsearch/document/KM00494510