Skip to content

Put the Remotes composer on the surface under a soft fade - #177

Draft
simonhamp wants to merge 5 commits into
mainfrom
feat/remote-composer
Draft

simonhamp wants to merge 5 commits into
mainfrom
feat/remote-composer

Conversation

@simonhamp

@simonhamp simonhamp commented Nov 15, 2026 •

Copy link
Copy Markdown
Member

The message composer at the bottom of a Remotes thread has the field across the top, growing to five lines, and under it a row with the + (photos, a voice note, Ping) on the left and a round Push button with an up arrow on the right, in your colour. Push is a muted circle while there's nothing to send, and the 1,600+ character count sits beside it.

This fixes Push being shorter than the field on iOS, since they're no longer side by side.

The bar

There's no box, border or hairline. On iOS the bar is Liquid Glass: the thread scrolls on under it and shows through blurred, so the bar is no longer a solid block. The glass fades in over the bar's top 28pt and runs on under the home indicator, so it has no hard top edge. On Android the field and its row sit on the surface as before, with the thread fading out above the bar through a 28pt gradient.

  • On iOS, <native:bottom-bar class="glass"> (Display::composerBarGlass()) asks mobile-air to draw the glass behind the whole bar. That needs a patched mobile-air (see below). The bar's first row is the fade, a gradient from see-through to the surface at 40%, and the rows under it have the surface at 40% (Display::composerSurface(), ComposerGlassTint). The tint keeps the glass close to the screen's own colour. Without it the glass came out a lighter grey than the screen in dark mode. A fill reaches under the home indicator, so the tint goes there too. The bar column itself still has no background, since mobile-air paints a bar's background colour behind the whole bar.
  • On Android the thread stops at the bar, so the fade lies over the foot of the thread, in the stack around it, and the bar is the surface. Nothing changed there.

EDGE's gradient stops don't get a dark companion the way bg-theme-* does, so Display::composerFade() builds them from theme('surface'), and the screen draws again on AppearanceChanged (the RedrawsOnAppearanceChange trait). I checked switching light and dark with the thread open.

The mobile-air patch behind the glass

EDGE's own glass class can't give a soft edge. On the rows it draws Liquid Glass in the element's shape, with a bright rim and some lensing along the top, it can't be faded, and it stops above the home indicator, where the thread showed through unblurred. So the glass comes from a small change to mobile-air's NativeRootTabsRenderer: when a bottom_bar carries glass, it draws glass behind the bar and through the bottom safe area, masked by a gradient so it fades in over the top 28pt. It's one file, about 50 lines. For now it's only applied in the vendor folder of the iPhone build, not opened upstream. Without it iOS still works, but the bar is just the 40% tint with nothing blurred behind it.

Things I tried first, with screenshots on the idea board:

  • glass on the rows in place of the surface. The rim and lensing make a hard line at the top, and the strip under the home indicator isn't covered.
  • The same with a 60% tint and the fade ending at 60%. The rim still shows.
  • iOS's own scroll edge effect, by switching the tabs renderer to .safeAreaBar. The automatic style draws a hairline. The soft style hardly blurs at the field's height, so a message behind the placeholder stays readable.
  • A 40pt fade instead of 28pt. In the longer ramp the content shows twice, sharp and blurred.

Shared with the commit page

composer-box (the field over a row of tools and the send button) and send-button are shared partials, which the reply bar on a commit's page uses in #180. composer-box takes $lead and $trail partials for the start and end of its row, in place of $counter: #180 puts the drop and the count in $trail, and the "post as" avatar from #182 fits in $lead. composer-fade, Display::composerBar() and Display::fadesInBar() do the fade, Display::composerBarGlass() and composerSurface() the glass, and Display::ComposerBoxBarHeight, ComposerFadeHeight and composerBoxGrowth() give a screen its clearance under the bar.

Other changes

  • The "folded in feeds" hint, and the FoldVertical icon before it, are gone from body-counter, so the composer sheet no longer says a long commit gets folded. The countdown near the limit stays. Commit::isFoldedInLists() and the preview constants had no other users, so they went too.
  • Picking two or three photos at once kept only the last one. A photo moved into the draft folder keeps its file time, often years ago, and until the draft holds it nothing does, so keeping the next photo pruned it as long forgotten. DraftImages::keep() now touches the kept file. This happens on main too. The commit page's new photo button in Commit screen: photos and preview in the reply bar, drop any time, related commits folded #180 showed it up.
  • The empty slots above the field (mentions, the reply strip, photos) are h-[0.1] when empty. On iOS an empty row took 10pt of the bar, and EDGE ignores a height of 0. The slots keep their keys and places, so the field doesn't move among its siblings and Android keeps the keyboard.

Everything else the composer did is unchanged: keep-focus, mention picking, the + menu, the voice note in the field's place, photos, the reply strip and Push's disabled states.

The text jumping as you type

Simon saw the reply field's text jump on the commit page, with the top line cut in half. It's the same text input here. The cause is in mobile-ui's iOS multiline input, not in the app, and #180 has the details and the upstream fix. Nothing in this PR drives the field's height while you type: PHP only sets max-lines, which never changes.

Gaps that need mobile-air or mobile-ui

  • Pushed screens in a tab pin their bottom bar with .safeAreaInset (NativeRootTabsRenderer) and paint the bar's background colour behind all of it, so a bar can't be partly see-through by itself. That's why the fade is the bar's first row on iOS.
  • Soft glass behind a bottom bar, faded in at the top and run on under the home indicator (the patch above).
  • Gradient stops have no dark companion (TailwindParser::parseGradientStop resolves theme-* in light only), hence the redraw on an appearance change.
  • A height of 0 is dropped on iOS (l.height > 0 in NodeLayoutModifier).
  • The iOS multiline text input's sizing (see Commit screen: photos and preview in the reply bar, drop any time, related commits folded #180).

Testing

Tested on an iOS 27.0 simulator (iPhone 18 Pro) and an Android 35 emulator against a local API, in light and dark, keyboard up and down: an image scrolled under the bar, a long message growing past five lines, mentions in an org thread (picking one kept the keyboard), and switching appearance with the thread open. On iOS I also typed at the medium and XXL text sizes. There's no Android shot of an empty field with the keyboard up; the long message with the keyboard up covers it. The glass I checked on the iOS simulator in light and dark, keyboard up and down, with photos scrolled under the bar, a long message and mentions. 1,906 tests pass, run serially.

Screenshots

The iOS After shots show the glass. Android is unchanged.

remotes-behind

iOS light iOS dark Android light Android dark
Before
After

remotes-keyboard

iOS light iOS dark Android light Android dark
Before
After

remotes-long

iOS light iOS dark Android light Android dark
Before
After

remotes-long-keyboard

iOS light iOS dark Android light Android dark
Before
After

remotes-mentions

iOS light iOS dark Android light Android dark
Before
After
  • No visible change

🤖 Generated with Claude Code

The field now sits across the top of a rounded box with the + and a round
Push button under it, like the Claude app's composer. That settles the old
height mismatch between the field and the Push button, and Push takes less
room. On iOS the bar is Liquid Glass tinted with the surface, so messages
scrolling behind it blur instead of showing through. Android keeps its solid
surface bar.

The box is a shared partial (composer-box, with send-button) so the commit
reply bar can move to it later. body-counter gains a text form of the fold
hint for that box, and the Remotes length counter moves into its own partial.

Empty slots above the box now take 0.1pt: on iOS an empty one took 10pt of
the bar, which showed as a gap once the bar had a backdrop.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
simonhamp and others added 3 commits November 18, 2026 00:13
The composer bar was a bordered box on Liquid Glass tinted at 70%, which
looked heavy, with a hard top edge. Now the field and its row sit straight
on the surface, and a 28pt gradient over the foot of the thread fades it
out above the bar on both platforms. Android gets the same fade, since it
lies over the scroll view rather than relying on a blur. EDGE's gradient
stops have no dark companion, so the stops come from theme('surface') and
the screen draws again on AppearanceChanged.

"folded in feeds" (and the FoldVertical icon before it) is gone from
body-counter, so nothing in the composers says a long commit gets folded.
The countdown near the limit stays.

composer-box takes $lead and $trail partials for the start and end of its
row, in place of $counter, so the commit page can put the drop and a
"post as" avatar there.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
On iOS the screen runs on under its bottom bar, so a fade lying over the
foot of the thread sat under the bar and never showed. The bar now draws
it as its first row there, and its rows (composer-rows) have the surface
of their own. The bar itself has no background on iOS: mobile-air paints
a bar's background colour behind the whole bar, which hid the fade. The
strip under the home indicator still shows the surface, from the scroll
view's background. Android keeps the fade over the foot of the thread,
since its screen stops at the bar.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Picking two photos from the library kept only the last. A photo moved
into the draft folder keeps its own time, often years ago, and until the
draft holds it nothing does, so keeping the second one pruned the first
as long forgotten. The kept file's time is now the time it was picked.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@simonhamp simonhamp changed the title Put the Remotes composer in one box on a blurred bar Put the Remotes composer on the surface under a soft fade Nov 18, 2026
On iOS the thread now shows through the bar, blurred, instead of
stopping at a solid surface. The bottom-bar carries glass, and a patched
mobile-air draws the glass behind the whole bar, under the home
indicator too, faded in over the bar's top 28pt so it has no hard edge.
The fade row ends at the glass's tint and the rows tint the glass with
the surface at 40%, so in dark mode the bar matches the screen.

EDGE's glass on an element can't do this: it draws a rim and lenses the
content along its top edge, and it stops above the home indicator, where
the thread showed through unblurred. Android is unchanged.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant