Accessibility#5
Merged
Merged
Conversation
A content-agnostic chrome hook: a layout implements floatingOverlay() (via HasFloatingOverlay) to float any element or Blade view above the content and tab bar, app-wide. Renders nothing when it returns null. Rides the existing chrome seam — ChromeContributorRegistry (PHP) + NativeRootHostRegistry (native) — so it ships entirely from the plugin with no edits to nativephp/mobile core. - FloatingOverlay builder (View|Element content, bottom/top, offset) - floating_overlay sentinel element + blade component pairing - HasFloatingOverlay / InteractsWithFloatingOverlay traits - iOS + Android NativeFloatingOverlayHost, registered as root hosts - registerFloatingOverlay() chrome contributor in the service provider - manifest component entry + tests Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Add keepFocusOnSubmit() (blade: keep-focus-on-submit / keep-focus). By default SwiftUI resigns first responder on return, dismissing the keyboard; opting in re-asserts focus so the keyboard stays up — the chat "send and keep typing" pattern. iOS TextInputCore re-focuses when the server value clears after submit.
Composed/inline text now inherits font size, weight and family from its context instead of resetting to defaults, and preserves Dynamic Type scaling (nuiScaledFont on iOS, includeFontPadding=false trim on Android) with lineLimit/maxLines honored.
Chat-style bottom anchoring: opens pinned to the bottom and re-scrolls to the latest content as it grows. iOS uses a ScrollViewReader + zero-height bottom anchor (deterministic, avoids the iOS 17+ .defaultScrollAnchor flakiness); Android re-triggers stick-to-bottom when subtree content changes.
Bare/Filled/Outlined inputs now fillMaxWidth() by default, matching the iOS renderer's maxWidth: .infinity. An explicit width in the modifier (FIXED layout mode) still wins since it composes later in the chain.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.