@butternutbox/pawprint-native 2.1.0 → 2.3.0

package/.turbo/turbo-build.log

@@ -7,12 +7,12 @@
 CJS Build start
 ESM Build start
 DTS Build start
-CJS dist/index.cjs     576.63 KB
-CJS dist/index.cjs.map 1.13 MB
-CJS ⚡️ Build success in 7532ms
-ESM dist/index.js     544.91 KB
-ESM dist/index.js.map 1.12 MB
-ESM ⚡️ Build success in 7532ms
-DTS ⚡️ Build success in 20401ms
-DTS dist/index.d.cts 113.87 KB
-DTS dist/index.d.ts  113.87 KB
+ESM dist/index.js     549.18 KB
+ESM dist/index.js.map 1.13 MB
+ESM ⚡️ Build success in 4938ms
+CJS dist/index.cjs     581.12 KB
+CJS dist/index.cjs.map 1.14 MB
+CJS ⚡️ Build success in 4947ms
+DTS ⚡️ Build success in 13475ms
+DTS dist/index.d.cts 114.40 KB
+DTS dist/index.d.ts  114.40 KB

package/CHANGELOG.md

@@ -1,5 +1,49 @@
 # @butternutbox/pawprint-native
 
+## 2.3.0
+
+### Minor Changes
+
+- d9b0195: Announce `IconButton` as a button to screen readers. It set a label but no
+  role, so VoiceOver read a drawer's close button as just "Close" with no hint
+  that it can be pressed.
+
+  Add `focusDate` to `DatePicker`. Setting it moves screen-reader focus to that
+  date's cell, after a short delay so VoiceOver doesn't ignore it. Consumers use
+  it to return focus to a picked date when a confirmation sheet closes, instead
+  of leaving VoiceOver on whatever iOS picks next.
+
+### Patch Changes
+
+- 2ecf870: Fix the drawer jumping when the keyboard opens, and stop scrolling from closing the keyboard.
+  - `Drawer.Body` now shrinks in step with the keyboard spacer instead of jumping to its final height a frame before the spacer arrives, so tall drawers no longer drop and snap back up as the keyboard opens.
+  - `Drawer.Body` scrolls the focused input into view once the keyboard has settled, so it no longer sits behind the footer.
+  - `Drawer.Body` defaults `keyboardShouldPersistTaps` to `"handled"`, so a drag that starts outside the focused input no longer dismisses the keyboard.
+  - `SelectField`'s dropdown now follows its field while the page scrolls. Consumers no longer need `keyboardDismissMode="on-drag"` and can drop it.
+
+## 2.2.0
+
+### Minor Changes
+
+- 55577eb: Make `DatePicker` days reachable with VoiceOver. The dates grid was a single
+  accessible element, so iOS only announced the month name and none of the day
+  buttons could be focused or selected. The grid is no longer grouped, and the
+  month label is now a header so screen-reader users can still jump between
+  months.
+
+  Add `getDateAccessibilityLabel(date, state, monthLabel)` so consumers can
+  announce delivery states such as the next box or future boxes. It defaults to
+  the existing "{day} {monthLabel}" label.
+
+### Patch Changes
+
+- 7d7caa7: Make `Drawer` usable with VoiceOver. The panel was a single accessible
+  element, so iOS hid everything inside it, including the close button and any
+  footer actions, and a drawer couldn't be closed or acted on. The panel is no
+  longer grouped, so its contents are reachable, and it stays modal to keep
+  focus inside. The VoiceOver escape gesture (two-finger scrub) now closes the
+  drawer, as Android back already does.
+
 ## 2.1.0
 
 ### Minor Changes

package/COMPONENT_GUIDELINES.md

@@ -702,21 +702,25 @@ on every render of the host component.
 
 #### Consumer requirements to document
 
-Both of these live on the _consumer's_ scroll container, not the component, so
-they must be stated in the component's documentation or they will be missed:
+This lives on the _consumer's_ scroll container, not the component, so it must
+be stated in the component's documentation or it will be missed:
 
-| Prop                                  | Why                                                                                                                                |
-| ------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------- |
-| `keyboardShouldPersistTaps="handled"` | Without it the first tap near a focused input is swallowed to dismiss the keyboard, and never reaches the row                      |
-| `keyboardDismissMode="on-drag"`       | Dismisses the keyboard on scroll, which blurs the field and closes the overlay rather than leaving it stranded at a stale position |
+| Prop                                  | Why                                                                                                           |
+| ------------------------------------- | ------------------------------------------------------------------------------------------------------------- |
+| `keyboardShouldPersistTaps="handled"` | Without it the first tap near a focused input is swallowed to dismiss the keyboard, and never reaches the row |
 
 `keyboardShouldPersistTaps` must be set on the **outermost** scroll container.
 React Native's responder capture follows the React tree root-downwards, so an
 outer `ScrollView` left at the default `"never"` captures the touch before any
 inner one is consulted — and a `Modal` does not isolate its contents, because the
-React tree is unchanged by it.
+React tree is unchanged by it. `Drawer.Body` defaults to `"handled"`.
 
-In DirectSalesApp, `WizardScrollView` and `app/(auth)/log-in.tsx` set these.
+Do **not** require `keyboardDismissMode="on-drag"` to keep an overlay attached.
+Closing the keyboard on every scroll is jarring in a form. An overlay positioned
+from its anchor re-measures while it is open and follows the anchor instead, as
+`SelectField` does.
+
+In DirectSalesApp, `WizardScrollView` and `app/(auth)/log-in.tsx` set this.
 
 ---