v0.17.0

25 October 2026Prerelease

Omaweb now requires omaweb-qtwebengine 6.11.2-16 or newer. That engine build carries the patches behind the clipboard and Google sign-in changes below. Your package manager pulls it in with the upgrade.
A theme's own mutedText colour is no longer read. Quiet text, such as tab titles, the footer and Omnibar rows, is now the theme's text blended 65% over the opaque sidebar and lifted to at least 4.5:1 contrast. Private windows get the same blend over the Private sidebar. pageMutedText is unchanged. If your theme set mutedText, that value no longer has any effect.

"Report a problem" in the Omnibar and in Settings › About opens GitHub's bug form in a new tab, with a Problem report already in its field. The report holds versions, what sites see, settings that differ from their defaults, Sync's state, extensions, the last crash and the tab you started from.
Addresses in the report are redacted. A query keeps its parameter names, and keeps a value only when it is a number or a plain word under 16 characters. Omaweb never sends the report itself.
When the form's link has to cut the report, the whole report is copied to the clipboard and the field asks you to paste it below.
omaweb report and the MCP tool print the same report. With no browser running, they print what can be read from disk and say what is missing.
"Record a problem" starts a Problem recording of the window's tabs. It keeps navigations, redirects, hand-offs to other apps, permission prompts and answers, console errors, failed loads and Omaweb's own warnings.
A recording is kept in memory only, for up to ten minutes. A mark in the sidebar footer shows while it runs. Selecting the mark ends the recording and opens the report with the recording in it.

A two-finger sideways swipe anywhere over the sidebar switches Space, in footer order, and wraps at both ends. The tab list follows your fingers and the neighbouring Space's own rows slide in beside it.
The switch happens if you release with the neighbour at least half in view, or flick towards it. Otherwise the list springs back.
A sideways wheel notch steps one Space.
The swipe does nothing in a Private window, with only one Space, or while a tab is being dragged.
While a Glance is open, its tab's row shows the Glance page's favicon in place of the speaker and close buttons. A Pinned tab shows a smaller tile over its corner. Pressing the favicon keeps the Glance as a tab.

Moving through the list with the arrow keys shows the selected row in the field. A search suggestion shows its words, a page shows its address, and a command or Space shows its name. Moving back above the first row, or pressing Escape once, restores what you typed. A second Escape closes the Omnibar.
Return now opens typed text in the Space on show. Another Space's tab is no longer selected by default. It stays in the list, and arrowing to it and pressing Return still switches to it.
The field's label says what Return will do: Open, Search, Switch to Tab, Run, or Switch to <Space> beside the Space's colour square.

Pages are drawn at the Page scale times the tab's own zoom. The Page scale follows the Desktop text scaling, read from the settings portal's text-scaling-factor and updated live, until you set it yourself.
Settings › Interface has a new pages group with a Page scale stepper, from 50% to 200% in 10% steps. While unset, it reads as the desktop's value, for example "136%, from the desktop".
The interface font size also follows the Desktop text scaling while you have not set one.
The zoom notice shows the tab's own zoom. Zoom stops where the combined size would leave the engine's 25–500% range.

A page that copies during a click or a key press now writes to the clipboard without asking. Copy buttons and Bitwarden's copy of a password work without a prompt. A write without a click or key press is still asked about.
An extension that declares clipboardWrite or clipboardRead uses the clipboard without a prompt.
Clipboard read is now a Site permission you can remember. The question offers allow once, always allow and block. Site information lists it as Clipboard, with a reset.

Google sign-in answers an unknown address with "Couldn't find this account" again, instead of "This browser or app may not be secure". The engine now defines chrome.app, chrome.csi and chrome.loadTimes on every page, as Chrome does.
Omaweb now sends an Accept-Language header with your first language, such as fi-FI, and navigator.languages matches it. A Private window sends the same value. Omaweb reads the language at launch, so a locale change applies on the next start.
Pages can no longer read or call the __omawebKeyboardNavigation, __omawebContentEditableEdited and __omawebMediaSession globals, or see the style sheets Omaweb adds. Before, any script could use them to tell the browser was Omaweb. Keyboard navigation, media keys and edit detection work as before.

The omaweb-git package names its launcher entry "Omaweb Dev", and About shows the git version, such as 0.16.1.r14.gc8c9084. The desktop file name and app ID stay the same, so switching between a release and a git build keeps your default-browser setting and window rules. The omaweb and omaweb-cli release packages are unchanged.

A page no longer reloads when Sync brings in another machine's state. A tab that comes back with the same address and Space keeps its page. A tab closed, moved or navigated on the other machine loads its new address. An open Glance also stays open through the update.
A page that hands off to an app by script rather than by a click now gets the "Open …?" prompt. Slack's desktop sign-in is one example. The app receives the address exactly as the page wrote it, with its original letter case. Only one prompt stands per tab at a time.
A link handed to a running Omaweb by another app now opens even when it contains encoded spaces or newlines. An escaped space at the end of a link is kept.
Omaweb now comes forward and takes focus when another app hands it a link, or when omaweb is run again with no address. It passes on the launcher's activation token to do this.
Sidebar and chrome buttons now rest in the theme's text colour, the same as the extensions button.
Scrollbars a site draws inside its own panels, as Jira does, are no longer replaced by the theme's colours.

Full changelog: https://github.com/villekivela/omaweb/compare/v0.16.1...v0.17.0