Repository navigation
Required: Home on phones #92
Description
Release: 0.8.0.
Owner: Sasha (@SashaMIT). Required for 0.8.0. Anders coordinates independent server review.
Done means
Release acceptance: Each exposed feature works clearly from start to end, including recovery. Keep unfinished or confusing features hidden until their complete journey passes. Hiding a feature does not complete its task; source checks alone do not establish installed acceptance.
- Home's top bar, Dock, launcher, search, controls, notifications and menus
work on a phone. Capsules fit the screen; Home pages, edit mode and the swipe
into Assistant work. - Desktop behavior remains accepted.
- Chromium and WebKit phone smoke checks pass on the exact candidate. Test: on the final integrated candidate,
node scripts/home-phone-layout-smoke.mjspasses on Chromium and WebKit. - A non-author reviews the server layout-sanitising change. Proof: Home on a phone: Home screen pages, phone title bars and stage, sheets, 44 px targets (phone-only) #116 (comment) and Home on a phone: Home screen pages, phone title bars and stage, sheets, 44 px targets (phone-only) #116 (comment)
- Sasha completes the final phone check after integration.
- The integrated G3 Community chat: Chat and People with Home #86/Chat and People: delivery states, Community catch-up and spam limits (follow-up to #86) #139 candidate passes Chat, People and Inbox at phone width: account creation, contact approval, exact conversation launch, draft/recovery controls and unread state. G3 Community chat: Chat and People with Home #86 owns the shared journey evidence; Home on a phone: Home screen pages, phone title bars and stage, sheets, 44 px targets (phone-only) #116 supplies this issue's phone layout.
- ~~Phone layout smoke turns a failed capsule measurement into null and then reports zero small targets; it must report incomplete coverage or fail (
scripts/home-phone-layout-smoke.mjs~1978 at 2cf55bd; review).~~ → moved to After 0.8.0 (not fixed at candidate f346147:measureCapsuleFramestill turns a failed measurement into null (:859) and the check counts it as 0 (:3187); a test-coverage gap, not a user-visible defect) Stream recovery: a successful fallback poll resets the reconnect counter and retries the stream; verify recovery under stream failure (review, correction).→ moved to After 0.8.0 (not fixed at candidate f346147; the repair stays with its owner per Home on a phone: Home screen pages, phone title bars and stage, sheets, 44 px targets (phone-only) #116 (comment); 0.8.0 does not offer opening Home from a phone, Required: Home on phones #92 (comment))- Keep the closed Assistant drawer outside the phone view with both normal and reduced motion. The drawer control opens and closes it clearly; the transcript, header and composer remain visible. Cover Chromium/WebKit at phone width and include this preference in Sasha’s exact-candidate installed check. Coordinate the existing Home on a phone: Home screen pages, phone title bars and stage, sheets, 44 px targets (phone-only) #116 change with LA-07: Make model state and recovery clear #101.
The earlier PR #116 work record is historical; that PR is closed without merge. The current candidate checks and remaining phone acceptance are recorded below. Sasha’s final phone check remains required.
Assistant reduced-motion finding — 2026-10-08
Source fixture evidence from #150: current develop 1828919980b1af1d60895c6cee178f769daed74c has the same stylesheet as the reviewed Local AI candidate 064c5729ad7e116cf1cc59f1a5b0c086ece7d28d. A settled Chromium fixture loaded current Assistant HTML and all five stylesheets with scripts removed and network blocked. At 390×844, with drawer class absent, aria-expanded=false and zero active animations, normal motion places the sidebar at −336..−16 px. Reduced motion places its opaque 320 px sidebar at 0..320 px and covers 308 px of the reply. The reduced-motion rule overrides the mobile closed transform. This is source fixture evidence; installed acceptance remains required. All fixture browser contexts closed. #150’s default-motion reply proof waits for the sidebar to leave the viewport and keeps this phone-preference correction with #92.
Browser plan reconciliation — 2026-10-08
#293 owns Browser viewer qualification on actual mobile hardware/client versions; desktop viewport smoke remains a layout result. #87 retains local Browser controls/accessibility, and #291 owns remote viewer workflows with input/reconnect/media/Close. Your Home phone-layout/server review and Sasha's final phone check retain their existing release scope.
Acceptance record
- Candidate: see 0.8.0: Release 0.8.0 #93.
- Exercised checks: the Wallet 44 px gap is fixed (
fd4152b6d); phone geometry checks pass on Chromium and WebKit at6ee5fa7f2(result). These are source fixtures, not installed-phone acceptance. - Real phones on alpha.21: iPhone (Sasha), Android (Anders).
- Remaining gate: Chromium and WebKit
home-phone-layout-smokeon the exact alpha.25 head; Sasha's phone check on alpha.25; Chat, People and Inbox at phone width.
Activity
andersalm commentedon Sep 29, 2026
Retained phone acceptance detail: test orientation changes, keyboard and touch input, and 200% zoom. Include app launch, focus/close, draft preservation and Inbox handoffs in the ordinary Home journey.
[-]0.7.1: Home on phones[/-][+]0.8.0: Home on phones[/+]andersalm commentedon Oct 10, 2026
Feature map (10 Oct, alpha.13, 390×844): the Dock overflows (6 of 10 icons visible; Chat, System, Bin off screen) and covers the bottom of windows; window close/minimise dots sit on app titles (Marketplace, Chat). Evidence: ~/.local/share/elastos-ops/hops/feature-map-20261010T011642Z/run1-click/shots/*-phone.png.
[-]0.8.0: Home on phones[/-][+]Required: Home on phones[/+]andersalm commentedon Oct 15, 2026
Status: the phone shell (#116) is not in any 0.8.0 RC; it was dropped from the Chat branch by b01464f and wrongly recorded as merged (#116 comment above). A phone gets the desktop shell squeezed to its width. Decision pending (Anders/Sasha): land it in a further RC or ship 0.8.0 without phone support and say so.
andersalm commentedon Oct 15, 2026
WebKit phone smoke (Linux box, Playwright 1.59.1 webkit-2272) on phone branch dfe0f1f: every surface matches Chromium except Wallet, where 4 buttons are below 44 px on WebKit only (Send 143x35, Receive 159x35, two secondary 71x29/73x29); tablet identical. Non-blocking (buttons work; tap-size polish) for 0.8.1. Chromium control PASS. Screenshots kept by OMP. Real iPhone/Android checks still needed from Sasha.
SashaMIT commentedon Oct 16, 2026
Real iPhone check (Sasha): phone Home looks right and works, no blockers. Android not checked.
andersalm commentedon Oct 16, 2026
Remaining for 0.8.0 (15 Oct 22:45 COT; final candidate alpha.21 = alpha.20 + automatic Community recovery; plan #93 6207232773): Sasha on a real iPhone (Safari) and Android phone (Chrome) on alpha.21; a disposition for the two open review boxes (smoke null measurement, stream recovery) before closing. The reduced-motion drawer is fixed since alpha.20; WebKit Wallet button size is 0.8.1.
andersalm commentedon Oct 16, 2026
Ticked with proof: desktop behaviour with the phone Home included: desktop shell smokes identical to base, and installed device checks on Mac and Linux passed on alpha.19 and alpha.21 (#87 6204914417, #89 6205121022, 6215379124); reduced-motion drawer: fixed in 9a05dae (alpha.20), the phone smoke asserts the closed drawer stays off screen with reduced motion. Sasha's real iPhone check passed with no blockers (6205947781 above); Android still to check on the final candidate.
changelog: 0.8.0 notes match what a new user gets: phone layout reach…
andersalm commentedon Oct 16, 2026
Real Android check (Anders, Galaxy S21 Ultra, Android 14, Chrome; 16 Oct). Home 0.8.0-alpha.21 from canary on a Mac, reached from the phone over USB (
adb reverse) at http://localhost:8091/home/. The Home GUI files are byte-identical in alpha.22 (f346147 changes only elastos-server, CHANGELOG and update-hop JSON). Sign-up created a passkey on the phone.PASS: sign-up with a phone passkey; Dock, pages, apps full screen, sheets, menus; installed to the home screen it opens full screen; Community posts both ways (phone → Mac Home and Mac → phone).
For 0.8.1 (none blocks 0.8.0, which does not offer opening Home from a phone; notes say so):
openTarget/focusWindownever callhideInboxRail; rail is min(392px, 100vw-16px) at z-index 100120). Same on desktop but hidden there. Smallest fix:hideInboxRail({ restoreFocus: false })inhome-gui.jsopenHomeGuiTargetfor non-inbox targets, plus a phone smoke step that taps Open. Also: Open does not switch Chat from a Direct conversation to Community (no Community navigate path).andersalm commentedon Oct 16, 2026
Milestone sweep (16 Oct, alpha.22):
scripts/home-phone-layout-smoke.mjs~:859.catch(() => null), ~:3187?? 0); test gap only. (2) stream recovery reset: moved to After 0.8.0; not fixed at f346147, repair stays with its owner (PR Home on a phone: Home screen pages, phone title bars and stage, sheets, 44 px targets (phone-only) #116 comment 6009336644).andersalm commentedon Oct 17, 2026
Source UI result for the unpublished candidate in #93’s Acceptance record: configured Chat passes all 31 scenarios, including native controls, refresh/reopen and link routing.
The unchanged fixture passes with Playwright 1.59.1’s matching Chromium 147; the default external Brave 154 pairing loses native iframe input. Use the matching browser for this source proof.
Installed phone acceptance and the required human experience checks remain open; this result supplies fixture evidence only.
andersalm commentedon Oct 17, 2026
The automated phone geometry checks now pass on 6ee5fa7: owner WebKit and Chromium runs both exit 0, each covering portrait, landscape and tablet (19/19/20 surfaces). All four phone runs report zero overflow and zero small Wallet targets.
Independent report inspection confirms that scope. Source binding uses the owner launch record and observed HEAD; fixture diagnostics remain, and tablet Wallet acceptance is unproven. Private receipt SHA256 93235bd6c5f6a206b8826d1f97af3e969e84ef1e60324cb8964cbec419ea09c0.
Sasha’s required phone experience and exact installed-package acceptance remain open; process teardown and the owner’s temporary-fixture cleanup still need their receipts.
wallet: phone buttons reach the 44 px touch target (#92 WebKit phone …
andersalm commentedon Oct 19, 2026
Codex owns the Marketplace title/control overlap and model detail phone geometry under #332. The source base is
3beb816438fd567145a8d725e22465bd83277cf0, tree5bc1173ec18ec947c40516f76917891f55301145. Chromium/WebKit source fixtures will have explicit source scope. Installed phone acceptance and Sasha’s final experience check retain their existing owners and gates.andersalm commentedon Oct 19, 2026
Marketplace source candidate
b1fff8bc690b1f3f6fabba2c1c280994912fbe86, treefb64fb56f25794629ee8f49cb0df24e4ab63b6f7, clears the title below the Home window controls at 640 px. Phone item detail buttons, Refresh and Technical details have 44 px targets. The matching Chromium Marketplace source fixture passes these checks and closed-detail keyboard traversal; each failed on the prior source. #332 holds the full source and installed-journey record.The full Home phone fixture is running on this exact source. Its results will retain their source-fixture scope. The cached matching runtime currently supplies Chromium; the final matching WebKit run, installed phone journey and Sasha’s experience check remain acceptance gates with their owners.
andersalm commentedon Oct 19, 2026
Candidate
b1fff8bc690b1f3f6fabba2c1c280994912fbe86(treefb64fb56f25794629ee8f49cb0df24e4ab63b6f7) passes the full Chromium Home phone source fixture: 19 portrait, 19 landscape and 20 tablet surfaces, plus closed-stream and stage-reset cases.The report retains its fixture diagnostics; WebKit and the exact-head remote gate are running, and the branch remains local.
Installed Marketplace Get, the integrated phone journey and Sasha’s final experience check remain open with OMP and their existing owners.
andersalm commentedon Oct 19, 2026
Candidate
b1fff8bc690b1f3f6fabba2c1c280994912fbe86, treefb64fb56f25794629ee8f49cb0df24e4ab63b6f7, passes the full Home phone source fixture on Chromium 1217 / Playwright 1.59.1 and WebKit 2336 / Playwright 1.62.1, each with 19 portrait, 19 landscape and 20 tablet surfaces.WebKit passed on one unchanged rerun with one built-in boot retry; its first external-link-probe boot timeout remains in the evidence. Fixture diagnostics and engine-specific probe skips remain in the reports, and all observed fixture processes have stopped.
The exact installed phone journey and Sasha’s final experience check remain open; OMP owns integration. The exact-head remote gate is still running.
andersalm commentedon Oct 19, 2026
Android Back white screen and Browser with no picture on the phone (items 1 and 4 of #92 (comment)) are now #456 (After 0.8.0).