-
Notifications
You must be signed in to change notification settings - Fork 674
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Native window.print() dialog is not handled #2331
Comments
Is there any update on this issue? |
Hi @ZayanNadeem The current development sprint is already planned. We will consider this issue during planning the next development sprint. |
Any update on this? |
Hi @weyert At present, this enhancement is not implemented. If this enhancement is very important for you, the PR is greatly appreciated. |
Hi, I'm just wondering if an issue I'm experiencing is related to this. Running my tests in headed mode (Safari, Chrome, Firefox), and I get a browser dialog/pop-up window: |
The setNativeDialogHandler method is intended for the native alert/confirm/prompt and beforeunload dialogs. It does not support the print dialog (as mentioned in this thread) or other dialogs. We will look deeper into it in the context of your other thread: #4732 |
Hey, can you leave this open, please? |
Hello @rob4629, OK. |
hi |
No updates yet. Once we get any results, we will post them in this thread. |
Hello, I'm experiencing the same problem. The print window is opened and the browser hangs and eventually closes down. Do you have any workarounds for this? The submit button doesn't have an onClick attribute. |
There are no workarounds. Once we get any updates, we will post them in this thread. |
Any update on this? please??? |
Hi @kerrijackson, There are still no updates. However, you can use the following workaround to prevent test execution from being stopped. Add the following code to clientScript. window.print = function () {}; |
Release v3.0.0-rc.2 addresses this. |
Are you requesting a feature or reporting a bug?
bug
What is the current behavior?
system print dialog appears and prevent test execution
What is the expected behavior?
this dialog should be handled
Provide the test code and the tested page URL (if applicable)
Test code
The text was updated successfully, but these errors were encountered: