Current webapp implementation sucks and PR 2121 should be revisited

[ramla]

As a Firefox based browser user, the current webapp implementation sucks. While removal of chromium entirely is another story and not within the philosophy of omakase, a chef should still be able to offer the basic choice between the only two common kinds of main ingredients so that it doesn't compromise the taste.

Currently if user sets Firefox (or even a non-listed chromium-based browser?) as the default browser and uses Discord the way Omarchy implemented it, links from Discord will always open in a Chromium window, which is extremely frustrating. The Learn links are also just links to webpages containing text, why should they even be launched as webapps?

I thank the creator of this PR 2121 for solving the problem for me. Later I found discussion 2468 but I shouldn't need to reach this far to find the solution to the basic question of default browser.

[alebak]

You're pointing at the right line. I've opened #8444, which generalizes this beyond the Firefox case.

Same root cause: omarchy-launch-webapp resolves the browser from xdg-settings with a hardcoded Chromium fallback and no override. Your thread wants the system default respected; others want the opposite — a webapp browser that is deliberately not the system default, chosen per app. Both are blocked by the same lookup.

The suggestion proposes a three-level cascade (system default → webapp default → per-app override) and a per-browser launch adapter, which is also what PR #4749's --isolate needs, since profile flags differ per browser family. Linking the threads so this stops being solved one special case at a time.