Skip to content

Own browser for web interfaces, and web pages in the tab - #8

Merged
Modding merged 4 commits into
mainfrom
own-browser
Nov 16, 2026
Merged

Modding merged 4 commits into
mainfrom
own-browser

Conversation

@Modding

@Modding Modding commented Nov 16, 2026

Copy link
Copy Markdown
Owner

What

Web interfaces (HTTP/HTTPS connections) can open in your own browser, inside the tab.

  • Settings » Web interfaces (src/app_web.rs): the program of any Chromium browser (Brave, Brave Origin,
    Vivaldi, Chromium, Opera) or Firefox browser (Firefox, LibreWolf, Waterfox, Zen …); the kind is recognised
    from the file name or chosen; the profile (own per connection in the data folder, own temporary, or the
    browser's normal one, which stays outside the tab); own arguments.
  • src/launch.rs: browser_family, web_profile_dir, web_args. Chromium browsers get --app and their
    own --user-data-dir; Firefox browsers -no-remote -profile <dir> -new-window and the window class
    MozillaWindowClass.
  • Every web interface opens in a tab by default (web_all_in_tab); before, only connections with
    Open in a tab ticked did, the others opened a separate browser window.
  • src/embed.rs: the window to embed is also searched among the processes the started one launched
    (descendants over a Toolhelp snapshot, at most 256), and src/app.rs keeps looking for 20 s after the
    first process ends — launchers and browsers that hand over to a child now land in the tab too.
  • --open web:URL for checks.
  • Roadmap item 12 (what is built, what is still to try; a built-in webview is ruled out by the Rust house
    rules), user guide in all five languages (settings chapter, protocols table, questions chapter), README,
    German README, translations in de, fr, it, uk.

Tested

  • cargo fmt --check, cargo clippy --all-targets --locked -- -D warnings, cargo test --locked
    (41 tests; new: browser kind, arguments for both kinds, profile folders, process tree incl. loops and the
    256 cap).
  • Live on Windows 11 with Edge: --open web:https://example.com — the page shows inside the tab
    (window picture taken).

Not tested

  • Brave / Brave Origin and a Firefox browser (not installed here).
  • Inside the tab, Chromium still shows its own title bar (minimise / maximise / close); listed in roadmap
    item 12.
  • Linux and macOS: unchanged behaviour (the system's browser), compiled only by CI.

Settings » Web interfaces: the program of any Chromium browser (Brave,
Vivaldi, Chromium, Opera) or Firefox browser (Firefox, LibreWolf, Waterfox,
Zen ...), its kind recognised from the file name or chosen, the profile (own
per connection in the data folder, own temporary, or the browser's normal
one, which stays outside the tab) and own arguments. Firefox browsers start
with -no-remote and their own profile so their window can be placed into the
tab (MozillaWindowClass). Roadmap item 12 records what is still to try.
- Every HTTP/HTTPS connection opens in a tab by default (Settings » Web
  interfaces » Open every web interface in a tab); before, only connections
  with "Open in a tab" ticked did, the others opened a browser window.
- The window to embed is also searched among the processes the started one
  launched (embed::descendants over a process snapshot), and the tab keeps
  looking for 20 s after the first process ends: launchers and browsers that
  hand over to a child no longer leave the page outside the tab.
- --open web:URL for checks. Tried live with Edge: the page shows in the tab.
…outside

The settings chapter names the new default (Open every web interface in a
tab) and the questions chapter says what to check when a web page still
opens in its own window. All five languages.
@Modding
Modding merged commit 82026fb into main Nov 16, 2026
5 checks passed
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