-
Notifications
You must be signed in to change notification settings - Fork 20
bug: custom app icons in dock open blank (backend engine) browser page #20
Comments
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. |
I have found a solution for this. Will work on this soon :D Yay |
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:
|
Bug confirmed. But this has nothing to do with that PR. Google must have changed something. |
@quanglam2807 OK thanks, I'll open a new issue. |
Bug Report
Specifications:
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:
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.
The text was updated successfully, but these errors were encountered: