Skip to content

Use a generic icon when webapp favicon lookup fails - #11393

Open
nicknack5050 wants to merge 1 commit into
omacom:quattrofrom
nicknack5050:fix/webapp-icon-fallback
Open

Use a generic icon when webapp favicon lookup fails#11393
nicknack5050 wants to merge 1 commit into
omacom:quattrofrom
nicknack5050:fix/webapp-icon-fallback

Conversation

@nicknack5050

@nicknack5050 nicknack5050 commented Sep 12, 2026

Copy link
Copy Markdown

When favicon discovery fails, installing a web app currently asks for another icon, and submitting an empty icon (or using a failing explicit icon URL) aborts installation. Use the theme's generic web-browser icon instead so a valid app name and URL are sufficient.

The interactive flow now asks only for name and URL. The CLI also accepts two arguments, while successful automatic downloads, explicit icon names/files, custom Exec commands, and MIME types retain their existing behavior.

Validation: the webapp install, escaping, and name suites pass, including new offline/failing-download cases for interactive installs, omitted icons, and explicit icon URLs. Bash syntax and git diff --check pass.

Full ./test/all: CLI suite passed; 228 of 236 shell test files passed. Failures: bar-icon-geometry, config, launch-about, locate, runtime-smoke, snapper, unowned-system-paths, and update-lock. Bar geometry and About failures were reproduced on clean upstream 31bd80d. Several checks require a sibling omarchy-pkgs checkout absent here. The other failures are reported without attributing a cause; the two branch suites were run concurrently in a live desktop environment. None of the webapp suites failed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant