Skip to content
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

App "freezes" after modal window with print options is closed/cancelled #21439

Closed
3 tasks done
clusterberries opened this issue Dec 9, 2019 · 2 comments
Closed
3 tasks done

Comments

@clusterberries
Copy link

Preflight Checklist

  • I have read the Contributing Guidelines for this project.
  • I agree to follow the Code of Conduct that this project adheres to.
  • I have searched the issue tracker for an issue that matches the one I want to file, without success.

Issue Details

  • Electron Version:
    • 5.0.12, 6.1.4
  • Operating System:
    • Windows 10
  • Last Known Working Electron version:
    • 5.0.2

Expected Behavior

Application responses to user actions after print is cancelled. (log statements are in the console)

Actual Behavior

Application doesn't handle events (e.g. click) after print is cancelled. (no log statements in the console)

To Reproduce

Precondition: clone this repository to reproduce the issue:
https://github.com/clusterberries/electron-sample/tree/print-page

$ git clone https://github.com/clusterberries/electron-sample.git -b print-page
$ npm install
$ npm start
  1. Click 'print me' button, so modal window appears
  2. Close or cancel modal window
  3. Click 'print me' and/or 'test' buttons
  4. Observe the console in dev tools.

Additional Information

The issue is not reproduced with Electon 7.1.3.

@codebytere
Copy link
Member

This is unfortunately known, and can't be fixed in 5-0-x given some changes that were made in Chromium at the time. 5-0-x is also only receiving security fixes at this time, so sadly, your best bet at this time is to upgrade to a version of Electron where this issue is not present.

@vladimiry
Copy link

Simply referencing the original and still open issue #19768.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants