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
{{ message }}
Repository navigation
Wishlist: please hint at potential issues with the adopted browsers in the "Add a new webapp" dialog #396
Different browsers have different takes at webapps and some more quirks are introduced by the browser+window manager combination. Some of these quirks are listed in the webapp-manager readme. Would be great to have a [?] button or a tool tip for the "browser" selector in the "Add a new webapp" dialog reporting the main quirks of the currently selected browser.
For instance, using Firefox as a browser with KDE there is a big issue in that the "KDE icons only task manager" appears to set the icon by the "program name" rather than the "window class". Hence, all the webapps get the "firefox" icon in the task manager rather than their right one. Furthermore, they get grouped with other Firefox windows, that is extremely inconvenient (now this may be an issue with the KDE plasma icon only task manager, but weirdly chrome and chromium don't have this issue).
Not having guidance in selecting the browser ends up in users picking one browser to then discover that it is too inconvenient to use, so they need to destroy the webapp and recreate it.
On the other hand Chrome/Chromium, seem to have another quirk with webapp-manager that appears worth displaying.
It is impossible to add new languages from the web app itself. The only way to do it seems to start a separate instance of chrome/chromium using the --user-data-dir parameter and the data dir that appears in the webapp desktop file. Then you configure the languages from there.
Activity
callegar commentedon Apr 28, 2026
On the other hand Chrome/Chromium, seem to have another quirk with webapp-manager that appears worth displaying.
It is impossible to add new languages from the web app itself. The only way to do it seems to start a separate instance of chrome/chromium using the
--user-data-dirparameter and the data dir that appears in the webapp desktop file. Then you configure the languages from there.