Hello TestProject Community,
Our QA team is having an issue dismissing a Chrome Print Alert for a Chrome Brower (Non-Headless) using a variety of the following Actions:
- Send “ESCAPE” to alert
- Send “ESCAPE” key(s)
- Clicks at “1” , “1” coordinates
- Presses and releases ESC (Robot)
- Dismiss alert (Robot)
- Click Element; tried creating Element Locators for the Cancel button on the Chrome Print modal, but TestProject can’t interact with it despite using CSSSELECTORS or XPATH.
We’ve tried a number of things to address this because we’d like to have our Automation Suite successfully passing Tests on Non-Headless and Headless browsers in parallel, but this scenario is posing some frustration.
- We need to dismiss the Alert so we can conduct subsequent Tests on the page thereafter. For context, it doesn’t seem like TestProject is able to interact with Chromes Print Alert after it is instantiated, hence the issue.
- We’d also like to avoid disabling the Print Alert. Ultimately the solution we’re trying to find is to exit the Print popup with the most “natural” workflow as much as possible to emulate the End User Experience.
Has anyone else encountered this scenario and were you able to resolve it?
Thanks in advance!