Skip to content
This repository has been archived by the owner on Sep 8, 2022. It is now read-only.

bug: custom app icons in dock open blank (backend engine) browser page #20

Open
scottrbaxter opened this issue Nov 5, 2020 · 5 comments
Labels
bug Something isn't working

Comments

@scottrbaxter
Copy link

Bug Report

Specifications:

  • App Version:
  • OS (macOS, Windows, Linux):

macOS 10.15.7
WebCatalog v25.12.0

Description:

Created a few custom apps using the Brave engine. I've added 2 icons to the macOS Dock. After a couple days, at some point clicking on an icon to open the app results in a new blank browser page opening. It will not open the homepage defined by WebCatalog.app, and also the app name in the menubar reflects the browser itself, and not the name provided by WebCatalog. Opening WebCatalog.app, I can click "Open" on the Installed tab, and a new icon appears at the far end of the macOS Dock. It seems as though some kind of backgrounded process is updating the app, but the Dock doesn't understand that the app has changed.

Steps to Reproduce:

  • Create custom app, using Brave engine. Open to make sure it works.
  • enable "Keep in Dock" for app
  • Close and Quit app, then wait >2 days
  • Click the Dock icon for this app, and it may show a blank website, and the browser backend engine name in the address bar, as well as bookmarks for the actual browser... which should not be related to this app in any way. Perhaps some kind of "open in default browser" is being executed incorrectly?

Additional Context

To band-aid this, I can simply remove each app (with this issue) from the Dock, open with WebCatalog, and "Keep in Dock" again, until whatever on the backend happens that causes this issue again. It seems to be every few days. I've been able to replicate it half a dozen times already.

@quanglam2807
Copy link
Member

This happens because of a limitation in the implementation of Chromium-based/Firefox engine. I haven't found a solution so we would have to live with it for now.

I'll try to write more about this soon so hopefully somebody else might have an idea to fix this.

@quanglam2807 quanglam2807 transferred this issue from webcatalog/webcatalog-legacy May 9, 2021
@quanglam2807 quanglam2807 added the enhancement New feature or request label Jun 5, 2021
@quanglam2807
Copy link
Member

I have found a solution for this. Will work on this soon :D Yay

@quanglam2807 quanglam2807 added bug Something isn't working and removed enhancement New feature or request labels Jun 5, 2021
@quanglam2807 quanglam2807 pinned this issue Jun 5, 2021
@chrisminett
Copy link

This issue is listed as open, but there was a commit merged above which is showing as being in v1.5.0+.

Since around that time, I find that clicking the doc icon for an open Chromeless app, using the Chrome engine, opens a blank Chrome window. Previously it would give the expected behaviour of opening the existing window. I'm running v2.0.0 but the issue occurred before updating to that version (I'm unsure exactly when this started).

Steps:

  • Open a Chromeless app, e.g. Google Meet, which runs the Google Chrome engine in a tabless mode.
  • The site is shown in a window.
  • Switch to any other app.
  • Cmd+Tab back to the Chromeless app; the existing window is shown (expected behaviour)
  • Switch to any other app.
  • Click the running dock icon for the Chromeless app; the Chromeless app is brought to the foreground and opens a new tabbed browser window over the existing open window. Shutting the new tabbed window shows the existing window behind.

@quanglam2807
Copy link
Member

Bug confirmed. But this has nothing to do with that PR. Google must have changed something.

@chrisminett
Copy link

@quanglam2807 OK thanks, I'll open a new issue.

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

No branches or pull requests

3 participants