0.2.0
0.1.9 shipped a regression: pages loaded into an embedded webview could not be scrolled. This release fixes that, silences the kernel's internal chatter, and corrects the release tooling that let 0.1.8 go out with unusable manifests.
Embedded webviews scroll again
The corner rounding for embedded webviews was reusing the chrome stylesheet, which carried two rules that only make sense for the app's own document:
html { background: transparent !important; overflow: hidden !important }
body { border-radius: …; overflow: hidden !important }
Injected into a third-party page, overflow: hidden on both html and
body disables that page's scrolling outright, and the transparent background
erased its own. Any site taller than the webview became unreadable.
The stylesheet is now split by role. The main webview (the app's chrome) keeps the transparent background and the hidden overflow; an embedded webview gets only the corner clip:
html { clip-path: inset(0 round …) }
Nothing else about the page is touched. Verified by loading a 4,800px-tall page in an embedded webview and scrolling it with the wheel: the content moves.
The kernel stops narrating its startup
Every launch printed the dispatcher registering each module, the startup marks, the control commands and a few diagnostics — around fifty lines before a window even appeared. That is profiling output, not something a person running an app should see.
OW_LOG_LEVEL controls it (silent, error, warn, info, debug) and now
defaults to warn. An app opts in from its own package.json, which the CLI
translates into the environment variable for ow dev and for the generated
.deb / AppImage launchers:
{ "owear": { "logLevel": "debug" } }
{ "owear": { "verbose": true } } is a shorthand for debug. A packaged
single-file binary inherits the variable from its environment.
A GLib critical on every bounds change
Replacing the corner stylesheet removed the previous sheet and unref'd it itself, which raced WebKit's own reference on the sheet and produced
GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
on the second webview.setBounds. The kernel is the only component that adds
style sheets to the content manager (the bridge injects scripts, not styles),
so it now clears the set and adds one, letting WebKit own the reference.
Release tooling: workspace:* can no longer reach npm
npm publish does not rewrite the workspace: protocol; pnpm does. Publishing
with npm therefore shipped manifests that every install rejects with
EUNSUPPORTEDPROTOCOL, while the publish itself reported success — which is how
0.1.8 came to be tagged and released without ever being installable.
tools/check-publish.mjs runs as prepublishOnly in all five packages and
aborts unless the publisher is pnpm (or the operator explicitly overrides with
OWEAR_ALLOW_NPM_PUBLISH=1). pack-runtime.mjs no longer suggests npm publish as the next step.
0.1.8 was never published to npm. 0.1.9 was the first working 0.1.x release, and it carries the embed-scroll regression this version fixes.
Not in this release
Isolated world on WebKitGTK (webkit_user_script_new_for_world) remains the
defense-in-depth item: with the document token, the origin lock and the
kernel-side enforcement in place, it no longer guards against anything that is
reachable today.