ZenNotes for Android 1.1.53: database Tables fit a phone better

Version 1.1.53, versionCode 56, November 2, 2026, following 1.1.52 (55), a same-day patch. PR #146 carries 25fa02a; the signed bundle zennotes-1.1.53-vc56.aab (40,087,343 bytes, SHA-256 971767cad90aacc08ddb3b5cb29902a177d9263301499b9ecf816fd9f67f4378) was built from that tree, and the merge commit 68e50e2 has the same tree.

What changes on the phone

• A long name stays readable in a database Table. The Open button no longer covers the end of it. The page icon left of the name opens the page.
• The Table's select boxes keep their room, and a Table with a long name opens at its first column instead of scrolled past them.
• The database header's tools stay on screen, on one line on phones from 360 px wide. On narrower ones they wrap and stay reachable.
• System Back closes Filter and Columns instead of leaving the database.

Under the hood

Core core-2.81.1-core.h4d33347386401068 was built by CI from ZenNotes/zennotes daedf423, the desktop v2.81.1 tag; core:adopt checked its provenance. The bridge contract adds no method. 1.1.52's stopgap CSS for the Table is gone, since core does it now, and table-touch.test.ts pins core's rules instead. The shell tightens the header's tools (4 px gaps, 6 px button padding), and useSystemBackClose gains a step for div[role="dialog"].z-popover, closed with an Escape from inside it; a menu above a popover still closes first.

Source: branch release/1.1.53 from main 3f67077: f60a090 (core 2.81.1), 4bf7bfc (stopgap removed), 989ae54 (1.1.53, versionCode 56), 0f97d3c and 8f00e1b (header), 25fa02a (Back).

Validation

• boundaries:check, npm run typecheck, 496 JavaScript tests, npm run build and npx cap sync android passed; bundleRelease was signed with the upload key on JDK 21, and the bundle reads md.zennotes 56 / 1.1.53, min 24, target 36.
• CI on #146: the build job and the emulator launch job passed on 25fa02a (run 41500708583).
• Walked on an Android 17 emulator (WebView 145) with generic data and real taps, on a debug build carrying the production web bundle so it could be measured over CDP, not on the signed bundle. Table at 411, 360 and 320 CSS px: first column on every open, select boxes 40 px, no Open over the name. Header one line at 411, 384, 375 and 360, wrapping at 320, every tool answering a tap at 360. Back closes Filter and Columns and stays on the database; with the keyboard up it takes one more press, and nothing sticks. Menus and sheets still close first, and plain Back still navigates. No crashes in the log.
• Known, not fixed: at 360 CSS px an active "Filter (1)" sends the ... menu to a second line, and the Filter popover's right border runs a few px off screen; its x stays visible and works.

Play Console submission

1.1.52 (55) is live. Production, Create new release: the AAB, processed as 56 (1.1.53), no devices lost (12,601 phones, 6,826 tablets), the usual no-deobfuscation-file warning. Release notes inside <en-US> tags, rollout 100%, saved, and sent for review on November 2; Publishing overview read Changes in review after a reload.

This release carries Play's signed universal APK from App bundle explorer as zennotes-1.1.53-universal.apk: 40,355,127 bytes, SHA-256 663786afa6e04b65c90badec6593c6a4b825fd9ea99528dddc2ca4b5f7eadee9, md.zennotes 56 / 1.1.53, min 24 / target 36, signer 9f1af3a4..., no CHECK_LICENSE, no pairip.

How to test locally

1. npm ci && npm run build && npx cap sync android, then open android/ in Android Studio and run on a device or emulator.
2. The circle, New..., New Database. Add a row named "Book the venue for the spring launch party and confirm catering".
3. Close and reopen it. Before: on a narrow phone the Table opened 40 px scrolled, with the select boxes off screen, and Open covered the end of the name. After: it opens at its first column with the boxes showing, and the page icon opens the page.
4. On a 360 px wide phone, look at the header: Filter, Columns, + Field, + Row and ... sit on one line.
5. Open Filter and press Back: it closes and you stay on the database. Press Back again: you leave the database. Columns behaves the same way.