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

Full screen breaks make Google Chrome unresponsive #800

Closed
3 tasks done
KarlBishop opened this issue Dec 11, 2020 · 4 comments
Closed
3 tasks done

Full screen breaks make Google Chrome unresponsive #800

KarlBishop opened this issue Dec 11, 2020 · 4 comments

Comments

@KarlBishop
Copy link

Prerequisites

Description

When returning to Google Chrome from a full screen break, the browser is unresponsive (can't scroll, click or continue typing).

Operating system: Windows 10

Steps to Reproduce

  1. Set Stretchly to full screen mode
  2. Use Google Chrome until a screen break occurs
  3. After screen break finishes, try interacting with website you were browsing

Expected behavior: All apps are responsive after Stretchly relinquishes control of the screen.

Actual behavior: Chrome is unresponsive after Stretchly relinquishes control of the screen.

Reproduces how often: 100%

Additional Details

If I transfer focus between applications - or Google Chrome instances - the browser becomes responsive again. For example, I can do this by alt-tabbing away and back again or briefly moving the mouse over a different window on the taskbar. The browser will then "catch up" with any scrolling/clicking/typing I did while it was unresponsive.

@hovancik
Copy link
Owner

I think this might be the same issue as #783. It should be fixed in next version.

@hovancik
Copy link
Owner

Can you try the new version?

@hovancik
Copy link
Owner

hovancik commented Jan 8, 2021

closing in favor of mentioned story

@hovancik hovancik closed this as completed Jan 8, 2021
@KarlBishop
Copy link
Author

Sorry, took me a while to get back to this - I'll add my followup on #783

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

No branches or pull requests

2 participants