You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Treat Chrome main window and installed PWA as separate apps.
Scenario when this would be used?
When using for example Chrome main window in one zone, and a PWA in other zone.
Supporting information
The option to "move newly created windows to last known zone" is great, because it disables the default Windows behavior of opening windows in cascade.
However, this option treats the main Chrome and the installed PWAs as the same program. I know that internally they are, but it would be great if FancyZones could differentiate between them. I usually use Chrome in one zone, for example, and the Gmail PWA in another, so I always have to move it manually.
The text was updated successfully, but these errors were encountered:
Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
Description of the new feature / enhancement
Treat Chrome main window and installed PWA as separate apps.
Scenario when this would be used?
When using for example Chrome main window in one zone, and a PWA in other zone.
Supporting information
The option to "move newly created windows to last known zone" is great, because it disables the default Windows behavior of opening windows in cascade.
However, this option treats the main Chrome and the installed PWAs as the same program. I know that internally they are, but it would be great if FancyZones could differentiate between them. I usually use Chrome in one zone, for example, and the Gmail PWA in another, so I always have to move it manually.
The text was updated successfully, but these errors were encountered: