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

Ctrl+W closes the PWA #443

Closed
bam80 opened this issue Jan 14, 2024 · 7 comments
Closed

Ctrl+W closes the PWA #443

bam80 opened this issue Jan 14, 2024 · 7 comments
Labels
bug Something isn't working

Comments

@bam80
Copy link

bam80 commented Jan 14, 2024

Description

The Ctrl+W shortcut is intercepted by browser and closes the PWA (as it's default shortcut to close a tab), even if it's used by the PWA itself.

Steps to Reproduce

  1. Open any installed PWA. Good example - Github's Codespaces.
  2. Press Ctrl+W
  3. The PWA window closes immediately

Additional Information

There is no such problem with Chromium PWAs - tabs in Chromium are also closed by Ctrl+W, but PWAs there handle the shortcut correctly and do not close the window.

Affected Websites

Environment

  • Operating system: Ubuntu 23.04
  • Desktop environment: Gnome
  • Installation method: DEB
  • Extension version: 2.9.1
  • Native version: 2.9.1
  • Runtime version: 121.0.1
  • Firefox version: 121.0
@bam80 bam80 added the bug Something isn't working label Jan 14, 2024
@bam80
Copy link
Author

bam80 commented Jan 14, 2024

I see there is a ac5032f but maybe make the default behavior in-sync with the Chromium one, to not confuse the users?

@filips123
Copy link
Owner

But if Ctrl+W is disabled by default, that may confuse Firefox users who expect it to close the tab (and the window if it's the only tab)...

@bam80
Copy link
Author

bam80 commented Jan 14, 2024

Well, as it's an "application" now it's more expected it would want to handle such combination itself.
Also, I think it's still better to keep this behavior consistent between different PWA vendors, as casual user shouldn't care much which vendor provides the PWA but just expects consistent behavior of the app itself.

My 2 cents.

@filips123
Copy link
Owner

Yeah, but I still think it's better to have the same shortcuts as normal Firefox. In any case, disabling the shortcut takes just a few clicks if you need it disabled. So, I'll close this issue.

Another possibility is to keep the shortcut normally enabled, but allow the website to overwrite it. I think this is what Edge (and probably Chromium) does. I may add another option for this (which may be enabled by default) in the future, but I cannot guarantee when, as first I want to clean up and improve some existing code.

@filips123 filips123 closed this as not planned Won't fix, can't repro, duplicate, stale Jan 15, 2024
@bam80
Copy link
Author

bam80 commented Jan 15, 2024

I may add another option for this

Let's make task/issue for that to track?

@filips123
Copy link
Owner

Ok, I will create it soon.

@filips123
Copy link
Owner

I created #446. Also, please comment there if you know any other shortcuts that are commonly used in PWAs and conflict with built-in Firefox options (apart from ones already on the list).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants