v0.15.0

Glance

• A Glance now stands the full height of the page area, with 12% margins at the sides and no head bar. Its close and "Open as tab" buttons sit in a pill beside the panel's top corner. The page beneath is scaled back to 0.96 and dimmed instead of blurred.
• Keeping a Glance as a tab now moves it into place. The panel grows to the width of the page area over 180 ms, the page beneath comes forward, and the new row in the sidebar lights up as it arrives. With chromeEase off it is still a cut.
• A kept Glance's tab lands right after the tab it came from. After a split it lands after both halves, and from a Pinned tab it lands at the head of the list. The page keeps its scroll position and typed text, because it is the same page.
• Nothing closes a Glance while it grows into its tab. If keeping stalls, it lets go within a second so the Glance can still be closed.
• An extension's popup takes the same look at its own size, centred. The command that keeps a Glance leaves a popup alone.
• A Glance in a Tab window has the new look too. Keeping it still opens a new Tab window, as a cut, since a Tab window has no sidebar.
• The sidebar no longer has a divider where it meets the page.

Extensions

• A page an extension opens with windows.create and Omaweb shows as one of your tabs is now treated by the engine as your tab. That covers a request opened as a tab with Glance off, in the Space on show or another Space or a Tab window, and a Glance you keep with "Open as tab". tabs.query lists the page among the browser's tabs, and tabs.remove refuses it like any other tab of yours.
• The extension is not told when its window becomes a tab. A Bitwarden passkey prompt kept as a tab stays alive.
• A Glance and an Auxiliary window are not tabs, and the engine is not told about them.

Command line

• omaweb help, omaweb --help and omaweb -h print the verbs, one line each, and how to launch the browser, then exit 0. They used to launch the browser on your profile. They never start the browser, open a profile or reach the control socket, and they still work after a leading option such as --json.
• omaweb help <verb> lists that verb's options, read from the same grammar the parser uses. A word that is not a verb is reported, and the command exits 2.

Engine

Omaweb now requires omaweb-qtwebengine 6.11.2-14 or later. This engine build carries the patches behind the favicon fix and the extension change above, and pacman installs it with Omaweb.

Fixes

• A favicon that follows the colour scheme, such as chatgpt.com's, now changes with a theme you switch while Omaweb runs. Before, it changed only after a restart. The page on show draws its icon again straight away. Any other page does so on its next visit and shows its earlier icon until then.
• Returning to Omaweb's Hyprland workspace no longer flashes dark over a page with a dark background and light content. Omaweb now keeps a picture of the page as you left it and shows that until the page draws again. In testing on the maintainer's machine, 0 of 50 returns showed a dark frame, down from 10 of 10. If the page was resized, changed display scale or moved to another document while away, the page's own colour shows instead, as before.
• The sidebar's background now reaches its edges. At 1.5x scale, a transparent column at the seam used to let the desktop show through.

Full changelog: https://github.com/villekivela/omaweb/compare/v0.14.0...v0.15.0