Skip to content

LordOS — a free, fast and secure GNU/Linux distribution based on Debian, with its own desktop environment: display server and Wayland compositor in C, a React UI engine on QuickJS, and private native apps.

Docs: who draws the frame, browsers by default, 0.8.4 changelog and screenshots

Federico Pereira62299e9cd8d4
diff --git a/CHANGELOG.md b/CHANGELOG.md
index f296ffe..bdcbf2f 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -10,6 +10,32 @@ of the matching [GitHub release](https://github.com/lordbasex/LordOS/releases),
## [Unreleased]
+## [0.8.4] - Unreleased
+
+### Changed
+
+- **Browsers with a single top bar.** Chromium and Firefox now draw their own bar, with the tabs in
+ the title bar and the window buttons inside it, instead of the LordOS frame on top. In Chromium
+ the buttons are LordOS's traffic lights (from LordOS's GTK theme, sized like LordOS's own frame);
+ Firefox keeps its own button style. Both put them where the LordOS theme does: on the left in Lord
+ Default, on the right in Classic, and follow a theme or light/dark change live. Going back to the
+ LordOS frame is one switch in each browser («Use system title bar and borders» in Chromium,
+ «Title Bar» in Firefox), and it now applies right away, without reopening the window. Systems
+ upgraded from 0.8.3 get the new defaults for Firefox, and for new Chromium profiles; an existing
+ Chromium profile keeps its frame until its user switches.
+
+### Fixed
+
+- **Two title bars in Chromium.** With «Use system title bar and borders» off, Chromium drew its own
+ bar and LordOS still put its frame on top: the compositor now honors the frame an app asks for
+ (xdg-decoration and the GTK 3 decoration protocol), also when it changes while the window is
+ open; the window keeps its place, size, maximized state, focus and Dock entry.
+- **Linux app windows disappeared after switching between Lord Default and Classic** (they stayed
+ open but invisible): they now come back in the new theme, maximized ones still maximized.
+- **The window menu of apps that draw their own bar.** A right click on a GTK app's own title bar
+ now opens the theme's window menu (Minimize, Zoom, Close; in Classic also Restore, Snap layouts
+ and the snap halves).
+
## [0.8.3] - Unreleased
### Added
diff --git a/docs/ROADMAP.md b/docs/ROADMAP.md
index c5ed55b..f804dbb 100644
--- a/docs/ROADMAP.md
+++ b/docs/ROADMAP.md
@@ -663,6 +663,27 @@ Details in `MAIL.md`. Tested on VM 123 against local Dovecot, Postfix and Radica
scope is restricted: until Google verifies the app, only up to 100 listed test users can sign in;
- Microsoft first: it is retiring password sign-in for IMAP, so OAuth will become the only way in.
+- [x] **Browsers with their own bar (0.8.4)** — lord-server honors the decoration mode an app asks
+ for (xdg-decoration and KDE's server-decoration), also while the window is open; Chromium and
+ Firefox draw their own bar by default, with LordOS's window buttons (traffic lights from LordOS's
+ GTK theme in Chromium), and the window menu, resize edges and snap layouts keep working. See
+ `docs/WAYLAND.md`, "Who draws the frame".
+- [ ] **Settings → Appearance: "Browsers: tabs in the title bar" (0.8.4, proposal)** — one switch,
+ on by default, that sets the browsers' own preferences for the user instead of each browser's
+ settings page:
+ - **Chromium:** writes `browser.custom_chrome_frame` (and `extensions.theme.system_theme` = 1, the
+ GTK theme, for the traffic lights) in each profile's `Preferences` under `~/.config/chromium`,
+ only while Chromium is not running (it rewrites the file on exit), through a narrow `lord.*`
+ call that edits those two keys and nothing else (never a free-form JSON write);
+ - **Firefox:** a `user.js` line `user_pref("browser.tabs.inTitlebar", 1|0)` in each profile under
+ `~/.mozilla/firefox-esr` (read at start, so it applies the next time Firefox opens);
+ - off → both go back to the LordOS frame; the page says the change applies when the browser
+ restarts;
+ - optional, separate: traffic lights in Firefox too. Firefox draws its window buttons itself (not
+ with the GTK theme), so it would need a per-profile `chrome/userChrome.css` plus
+ `toolkit.legacyUserProfileCustomizations.stylesheets`; weigh it against touching browser
+ profiles before doing it.
+
## After the final ISO
- [ ] **AI assistants through MCP, with permissions** (study first, then build). Let an AI
diff --git a/docs/UPDATES.md b/docs/UPDATES.md
index d860737..804cb70 100644
--- a/docs/UPDATES.md
+++ b/docs/UPDATES.md
@@ -196,6 +196,7 @@ Today's migrations:
| `001-0.8.1-network-permissions` | Enables `lord-netperm.service` (per-app network permissions) where `lordos.service` is enabled. The ISO, the Pi image and `install.sh` already did; a system set up with `apt` alone had it off. Runs once: disabling it later sticks. |
| `002-0.8.1-root-ssh-keys` | 0.8.1 adds `PermitRootLogin no` (`/etc/ssh/sshd_config.d/10-lordos.conf`). On an **upgrade** from 0.8.0 with SSH installed and keys in `/root/.ssh/authorized_keys` (a VPS run as root), it writes `09-lordos-root-keys.conf` with `PermitRootLogin prohibit-password`, so root keeps logging in with keys (never passwords) instead of being locked out at the next restart. New installs never get it; delete the file to apply LordOS's default. |
| `003-0.8.2-drivetemp` | 0.8.2 ships `/usr/lib/modules-load.d/lordos-drivetemp.conf` (SATA disk temperatures in Monitor → Disks, read at boot). On a running system it loads `drivetemp` once, so the temperatures show without a restart. Does nothing without systemd (an image being built) or where the kernel has no `drivetemp`. |
+| `005-0.8.4-browser-frames` | 0.8.4 makes the preinstalled browsers draw their own bar with LordOS's window buttons (`WAYLAND.md`, "The browsers by default"). Where `/etc/chromium/master_preferences` still has the 0.8.3 ISO's `"custom_chrome_frame": false` it becomes `true` and the GTK theme is added (new Chromium profiles only); where `/etc/firefox-esr/lordos.js` is still exactly the 0.8.3 file it becomes `inTitlebar` 1 (every Firefox profile whose user didn't change «Title Bar»). Anything an administrator changed is kept; home folders are not touched. |
**Settings migrations** (each user), in `sdk/settings.js`: `MIGRATIONS` is a list of
`[schema, (settings) => newSettings]` applied in order when the session loads
diff --git a/docs/VM-SETUP.md b/docs/VM-SETUP.md
index e34cd86..a594077 100644
--- a/docs/VM-SETUP.md
+++ b/docs/VM-SETUP.md
@@ -1317,3 +1317,33 @@ package's files by `~/deploy-remotesec-122.sh` (it saved `/usr/lib/lordos`, `/et
back to `lord` (the autologin had changed it), `rtest` and its home deleted, the tree, the scripts
and the backup removed, `lordos.service` restarted on the package's 0.8.2 binaries, at the login
screen. Network untouched.
+
+## Step 37 — 0.8.4: browsers with their own bar (VM 119 `lordos-spot`, October 19)
+
+See `WAYLAND.md` ("Who draws the frame", "The browsers by default"). On VM 119 (172.17.0.54), tree
+in `~/LordOS-csd`, built there (`make -C server`, `make -C server build/deco-client`,
+`make -C server test`) and installed over `/usr/lib/lordos` by `~/deploy-csd-119.sh` (it saved
+`/usr/lib/lordos`, the original `/etc/chromium/master_preferences` and `settings.json` first, in
+`/var/backups/lordos-csd-bak`).
+
+- **Installed for the tests:** `gsettings-desktop-schemas` (the ISO has it; without it GTK 3 can't
+ read the theme and the button layout from the keyfile backend, and Chromium's GTK theme shows
+ Adwaita's buttons on the right), removed at the end. `assets/gtk/LordOS*` copied to
+ `/usr/share/themes/` (the package does that), removed at the end.
+- **Session:** `/etc/lordos/session.conf` with `AUTOLOGIN=lord` (it didn't exist; removed at the
+ end), English, light, Lord Default in `settings.json` (restored at the end).
+- **Browsers:** throwaway profiles in `/tmp` (`chromium --user-data-dir=/tmp/csd-chr2`,
+ `firefox-esr --profile /tmp/csd-ff --no-remote`), started from SSH with the session's environment
+ (`WAYLAND_DISPLAY=wayland-0`, `XDG_SESSION_TYPE=wayland`, `GSETTINGS_BACKEND=keyfile`, the session
+ bus). The user's own browser profiles were not touched. `master_preferences` was edited to test the
+ new initial preferences on a new profile and put back.
+- **Input and screenshots:** `lord-qmp-input.py 119 1280 800` and `lord-type.py 119` from the host,
+ `screendump` holding `flock /tmp/sistema-119-screen.lock`. The "before" screenshot ran the saved
+ October 18 install for a few minutes, then the new build again.
+- **The migration** (`005-0.8.4-browser-frames.sh`) ran against copies under a scratch root
+ (`LORDOS_MIGRATION_ROOT`): the 0.8.3 files change, a second run changes nothing, files an
+ administrator edited stay.
+- **Undone at the end:** `/usr/lib/lordos` restored from the backup (`diff -r` empty),
+ `master_preferences` and `settings.json` restored, the themes, the schemas package, `session.conf`,
+ the profiles, the tree, the script and the backup removed, `lordos.service` restarted to the login
+ screen. No network or Proxmox setting was touched.
diff --git a/docs/WAYLAND.md b/docs/WAYLAND.md
index acbec97..056646d 100644
--- a/docs/WAYLAND.md
+++ b/docs/WAYLAND.md
@@ -36,13 +36,15 @@ Apps that only speak X11 open through Xwayland, started on demand, with our own
| `wl_data_device_manager` | 3 | clipboard shared with LordOS's in both directions (see below) |
| `zwp_primary_selection_device_manager_v1` | 1 | primary selection: select to copy, middle click to paste (0.8.3, see "X11 apps") |
| `xdg_wm_base` | 6 | windows (`xdg_toplevel`: title, move, resize, maximize, minimize, close) and popup menus (`xdg_popup` with `xdg_positioner`: anchor, gravity, flip and slide within the screen) |
-| `zxdg_decoration_manager_v1` | 1 | apps that use it (Qt, foot, Kitty, Alacritty) leave the frame to the theme |
+| `zxdg_decoration_manager_v1` | 1 | the app picks who draws the frame: server side (Qt, foot, Kitty, Alacritty: the theme's frame) or client side (Chromium with its own bar), also while it's open (0.8.4) |
| `wp_cursor_shape_manager_v1` | 1 | the app asks for the cursor by name (Chromium, GTK 4, Qt 6) and LordOS draws its own (`cursor.c`, see `WINDOWS.md`) |
Windows enter the SDK's window manager (`sdk/wayland.js`) as the internal app `linux` (id
`linux#<surface>`): the theme sees them like any other, with their title, focus, maximize,
-minimize and Dock. Those that draw their own frame (GTK) arrive with `args.csd` and the theme
-shows only the content (both bundled themes already do). The keyboard goes to the frontmost Linux
+minimize and Dock. Those that draw their own frame (GTK, and the browsers with their own bar) arrive
+with `args.csd` and the theme shows only the content (both bundled themes already do); an app that
+switches while open sends `deco` and the same window changes presentation (see "Who draws the
+frame" below). The keyboard goes to the frontmost Linux
app; ❖ combinations still belong to LordOS.
## How to open an app
@@ -166,24 +168,87 @@ resizing (see `WINDOWS.md`).
| | |
|---|---|
-| ![chromium](decorations-chromium.png) | ![firefox](decorations-firefox-dark.png) |
-| Chromium with the LordOS frame (without its own window buttons) | Firefox ESR with the LordOS frame, dark |
+| ![chromium light](chromium-csd-light.png) | ![chromium dark](chromium-csd-dark.png) |
+| Chromium with its own bar (0.8.4 default): tabs in the title bar and LordOS's traffic lights on the left, from LordOS's GTK theme | The same in dark: it follows the mode live |
+| ![before](chromium-csd-before.png) | ![classic](chromium-csd-classic.png) |
+| Before 0.8.4: Chromium asked to draw its own bar and LordOS put its frame on top anyway (two bars) | The Classic theme: the buttons go to the right (`:minimize,maximize,close`), switched live |
+| ![firefox](firefox-csd.png) | ![own theme](chromium-own-theme.png) |
+| Firefox ESR with its own bar: LordOS's order and side, drawn in Firefox's own style | Chromium with its «Classic» theme (not GTK): LordOS's order and side, Chromium's own buttons |
| ![gtk dark](decorations-gtk-dark.png) | ![gtk light](decorations-gtk3-light.png) |
| Mousepad (GTK 3, «LordOS-dark» theme) and GNOME Calculator (GTK 4/libadwaita, green accent and buttons on the left), dark | The same in light: they change live when the mode is switched in Settings |
-| ![firefox light](decorations-firefox-light.png) | |
-| Firefox switched to light live | |
-
-- **Chromium.** It uses the theme's frame if it asks for server-side decoration
- (`zxdg_decoration`). The ISO ships `"browser": { "custom_chrome_frame": false }` in
- `/etc/chromium/master_preferences` («Use system title bar and borders»), which applies to new
- profiles. It goes back to its own bar in Settings → Appearance.
-- **Firefox ESR.** The ISO ships `/etc/firefox-esr/lordos.js` with
- `pref("browser.tabs.inTitlebar", 0)`. Firefox draws with GTK 3, which doesn't speak
- xdg-decoration: lord-server also advertises **`org_kde_kwin_server_decoration_manager`**
- (KDE's) with «server» mode as the default. So GTK 3 asks LordOS for the frame for windows
- without their own bar (Firefox, Mousepad). The protocol tables are hand-written in `wl.c`,
- without plasma-wayland-protocols' XML. Firefox's bar comes back in Customize Toolbar →
- «Title Bar».
+
+### Who draws the frame (0.8.4)
+
+An app chooses; LordOS **prefers** its own frame and honors the app's answer.
+
+- **xdg-decoration** (Chromium, Qt, foot): the first `configure` says `SERVER_SIDE`. If the app then
+ asks `set_mode(CLIENT_SIDE)` it gets `CLIENT_SIDE` and draws its own bar; `set_mode(SERVER_SIDE)`
+ and `unset_mode` give the theme's frame. Destroying the decoration object means the app draws its
+ own frame again (the protocol's rule).
+- **`org_kde_kwin_server_decoration`** (GTK 3, so Firefox and Mousepad): default «server»;
+ `request_mode(client)` is answered «client».
+- **Live.** When an open window changes mode (Chromium's «Use system title bar and borders»,
+ Firefox's «Title Bar»), lord-server sends JS a `deco` event (`{ csd }`) and `sdk/wayland.js` sets
+ `args.csd` on the **same** window (`wm.setArgs`): place, size (the outer frame stays where it was;
+ the content grows or shrinks by the theme's bar and the app gets a `configure`), maximized state,
+ focus and Dock entry don't change.
+- **Before 0.8.4** lord-server answered `SERVER_SIDE` whatever the app asked. Chromium with its own
+ bar then drew its tab strip and buttons and LordOS put its frame on top: two bars.
+- Tested with `build/deco-client` (`server/tests/deco_client.c`, run inside a session): every mode
+ request in both protocols, before and after mapping, with the `xdg_surface.configure` that must
+ follow; `build/deco-client hold 6` keeps switching a window to watch the theme.
+
+What a window with its own bar still gets from LordOS (both themes, `WINDOWS.md`):
+
+- the invisible resize edges around it and the theme's shadow (the app's own shadow is clipped
+ with its window geometry);
+- moving from its bar (`xdg_toplevel.move`), resizing from its edge (`xdg_toplevel.resize`),
+ maximize, restore and minimize from its own buttons, double click on its bar (the app asks to
+ maximize);
+- **the window menu**: a right click on a GTK headerbar asks `xdg_toplevel.show_window_menu`, and
+ the theme shows its menu at that point (`w.windowMenu`, `wm.showWindowMenu`): Lord Default the
+ menu bar's Window items (Minimize, Zoom, Close Window), Classic its title bar menu plus **Snap
+ layouts**, which opens the same flyout its maximize button shows on hover (an app's own maximize
+ button can't). Chromium shows its own menu on its tab strip instead (with «Use system title bar
+ and borders» in it);
+- the window-button layout LordOS publishes to GTK (`button-layout`, below), which Chromium and
+ Firefox follow live when the theme changes;
+- the things LordOS draws that never lived in the frame: the «Remote desktop: user · IP» badge is a
+ screen overlay (`sdk/remote.js`, notification layer) and a protected window is black in captures
+ through its content node (`AppHost`), so both work the same for these windows.
+
+| | |
+|---|---|
+| ![window menu](csd-window-menu.png) | ![snap layouts](csd-snap-layouts.png) |
+| GTK Demo (own frame): right click on its bar, Lord Default's window menu | Classic: the window menu's «Snap layouts» on an app with its own bar |
+
+### The browsers by default
+
+- **Chromium.** The ISO ships `/etc/chromium/master_preferences` with
+ `"browser": { "custom_chrome_frame": true }` (its own bar) and
+ `"extensions": { "theme": { "system_theme": 1 } }` (the **GTK** theme): new profiles draw the tab
+ strip in the title bar with the window buttons from LordOS's GTK theme, so they are LordOS's
+ traffic lights (13 px circles, 8 px apart, glyph on hover, grey when the window isn't focused).
+ Tested: a new profile starts that way. Back to the LordOS frame: Settings → Appearance → «Use
+ system title bar and borders» (or right click on the tab strip). With Chromium's «Classic» theme
+ the buttons keep LordOS's order and side but are Chromium's own.
+- **Firefox ESR.** `/etc/firefox-esr/lordos.js` has `pref("browser.tabs.inTitlebar", 1)`: its own
+ bar, with the window buttons in LordOS's order and side (it reads the same `button-layout`), drawn
+ in Firefox's own style: Firefox draws those buttons itself, not with the GTK theme, so they aren't
+ traffic lights. Back to the LordOS frame: Customize Toolbar → «Title Bar». Firefox draws with GTK
+ 3, which doesn't speak xdg-decoration: lord-server also advertises
+ **`org_kde_kwin_server_decoration_manager`** (KDE's), with «server» as the default mode, so GTK 3
+ windows without their own bar (Firefox with «Title Bar», Mousepad) ask LordOS for the frame. The
+ protocol tables are hand-written in `wl.c`, without plasma-wayland-protocols' XML.
+- **Upgrades** (migration `005-0.8.4-browser-frames`): where the files are still what the 0.8.3 ISO
+ wrote, they change to the new defaults. Firefox's is a default pref, so every profile follows it
+ except one whose user changed «Title Bar». Chromium's are initial preferences: only new profiles
+ get them; an existing profile keeps its frame (switch as above, and Settings → Appearance → Theme →
+ «Use GTK» for the traffic lights). Home folders are never touched.
+- **The LordOS GTK theme's title buttons** (`assets/gtk/LordOS*/gtk-3.0/gtk.css`): GTK sizes a title
+ button by its 16 px icon, and Chromium does the same when it draws its tab strip with the GTK
+ theme, so the button stays 16 px and the circle is a 13 px radial gradient inside it; measured on
+ the VM: 12–13 px circles, 21 px from center to center, like LordOS's own frame.
- **GTK 4 / libadwaita (GNOME).** They read the mode, the accent and the button order from
**`org.freedesktop.portal.Settings`**. lord-server itself serves it (`server/src/ui/portal.c`)
on the session bus, without xdg-desktop-portal, with Passwords' own D-Bus client
@@ -202,14 +267,16 @@ resizing (see `WINDOWS.md`).
with LordOS's colors, bar and traffic lights.
- GTK 3 has no accent: its own stays blue.
- **The buttons** go on the left in traffic-light order (`close,minimize,maximize:`). The Classic
- theme asks for them on the right with the `gtkButtons` token (`:minimize,maximize,close`).
+ theme asks for them on the right with the `gtkButtons` token (`:minimize,maximize,close`). GTK
+ apps, Chromium and Firefox move them live when the theme changes.
- **Qt/KDE.** They use the theme's frame (xdg-decoration). Qt 6 also reads `color-scheme` from the
portal; not tested.
- **The JS.** The SDK's `ThemeProvider` sends mode, accent and buttons with `lord.portal.set` when
they change.
Tested in VM 118 with Chromium 155, Firefox ESR 153, Mousepad (GTK 3) and GNOME Calculator
-(GTK 4, libadwaita).
+(GTK 4, libadwaita); the 0.8.4 frame changes on VM 119 (`VM-SETUP.md`, step 37) with Chromium 155,
+Firefox ESR 153, GTK Demo (GTK 4) and foot, both themes, light and dark.
## X11 apps (Xwayland)
@@ -332,6 +399,11 @@ display.
## Pending
+- **Firefox ESR 153 ignored mouse clicks on VM 119** (October 19, QEMU's USB tablet through QMP):
+ the pointer reaches it (`enter`, `motion`, `button` on its content subsurface, checked with
+ `WAYLAND_DEBUG`) and the keyboard works, but buttons, menus and pages don't react; the same with
+ the build installed before (October 18) and with the LordOS frame, so it isn't the frame. To
+ investigate (two `wl_seat` bindings from the same client get the events twice).
- SVG app icons (most modern GTK/Qt apps only ship SVG).
- Opening files with a Linux app (`%f`/`%u`), `.desktop` actions and terminal apps.
- Already done (see `GPU.md`): `linux-dmabuf` v4, GPU composition (Mesa, optional), direct
diff --git a/docs/chromium-csd-before.png b/docs/chromium-csd-before.png
new file mode 100644
index 0000000..a52fa2f
Binary files /dev/null and b/docs/chromium-csd-before.png differ
diff --git a/docs/chromium-csd-classic.png b/docs/chromium-csd-classic.png
new file mode 100644
index 0000000..cd72ef9
Binary files /dev/null and b/docs/chromium-csd-classic.png differ
diff --git a/docs/chromium-csd-dark.png b/docs/chromium-csd-dark.png
new file mode 100644
index 0000000..f69ac3c
Binary files /dev/null and b/docs/chromium-csd-dark.png differ
diff --git a/docs/chromium-csd-light.png b/docs/chromium-csd-light.png
new file mode 100644
index 0000000..8b72028
Binary files /dev/null and b/docs/chromium-csd-light.png differ
diff --git a/docs/chromium-own-theme.png b/docs/chromium-own-theme.png
new file mode 100644
index 0000000..29d2530
Binary files /dev/null and b/docs/chromium-own-theme.png differ
diff --git a/docs/csd-snap-layouts.png b/docs/csd-snap-layouts.png
new file mode 100644
index 0000000..bcd9653
Binary files /dev/null and b/docs/csd-snap-layouts.png differ
diff --git a/docs/csd-window-menu.png b/docs/csd-window-menu.png
new file mode 100644
index 0000000..5f79baa
Binary files /dev/null and b/docs/csd-window-menu.png differ
diff --git a/docs/firefox-csd.png b/docs/firefox-csd.png
new file mode 100644
index 0000000..7061dbd
Binary files /dev/null and b/docs/firefox-csd.png differ