Make every ZIP reachable on mobile #24
Loading…
Reference in a new issue
No description provided.
Delete branch "codex/issue-5-mobile-file-list"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
A phone can report three received ZIPs while the sidebar height limit clips the last entry, especially with upload help expanded. This gives the ZIP list its own labelled native scroll region and lets the mobile controls grow above it, with the selected status panel below.
Closes #5; coordination follows #14. Source-development closure retains the documented native release and actual-device/installation checks. Based on merged main
44c36de10d3c4c8a4a72c01750e20bd2e88ab969; feature commite274c617aa64ace46a6a53a558de717083f37545. Held #12/PR #19 are unchanged.Validation passed:
npm --prefix ui run lint,npm --prefix ui run build, and fullnpm --prefix ui audit(zero reported vulnerabilities).node ui/tests/mobile-file-list.mjs: 3/16 ZIPs, long names, expanded help, 320/390/760/761/1280px, selection/remove hit targets, emulated touch drag/tap, keyboard scrolling/Enter/Space/Tab, selection retention, local removal, independent owner-session monitoring and outage/reconnect.task-activity.mjs,task-email.mjsandadvanced-import.mjsbrowser suites.tests/container_smoke.py --skip-build --image immich-bridge:issue-5-app --runner-image immich-bridge:issue-13-runner --processor-image immich-bridge:issue-13-processor --browser: real uploads, replacement/resume/SHA-256, queue/SQLite, UI pause/stop/reselection, reports, settings and redaction. Backend/runner/processor/importer source is unchanged from merged #13; its runner/processor images were reused. Disposable containers/volumes were removed.The existing UI bundle-size advisory remains. Local Chrome/Chromium with emulated touch does not certify physical devices, Safari, native ARM64 or the Forgejo release gate. No release images were published and no deployed service or active upload/task was interrupted. Next: review, satisfy native CI, then coordinate installation and the recorded device/pilot checks.
WIP: Make every ZIP reachable on mobileto Make every ZIP reachable on mobileIndependent merge-readiness review completed for
e274c617aaagainst main44c36de. No blocking findings in the application, CSS, regression harness or documentation diff. Re-ran UI lint/build, full dependency audit (zero vulnerabilities), mobile-file-list, task-activity, task-email and advanced-import browser suites; all pass. All nine CI policy tests plus source/workflow/document contracts, clean-tree and diff checks pass. Fresh synthetic 320px status and long-list screenshots were inspected. The merge is conflict-free and its calculated tree equals the validated feature tree; backend/importer/runtime build sources are unchanged. Earlier full disposable container/upload evidence remains documented in #5 comment 370 and was not rerun during this source review.Native Forgejo run 23 is waiting; it is not a successful native AMD64/ARM64 or release-gate result. No branch-protection rules were changed, no force merge is requested, and release/actual-device/installation checks remain required. The owner requested this source merge; the draft marker has been removed. Held #12/PR #19 is excluded. No deployment, release-image publication or active-work interruption is authorized or performed.