@declarion/react 0.47.0 → 0.48.1

package/dist-lib/lib/actions.d.ts

@@ -96,11 +96,19 @@ export declare function actionNeedsConfirm(action: Action | undefined): boolean;
  * Precedence: disabled-reason > description > name.
  *
  * A labeled control already shows the name, so its tooltip is the description
- * alone; an icon-only control (`display.icon_only`) has no visible label, so it
- * shows "name - description" to keep the name reachable on hover. Absent
- * description falls back to the name - byte-identical to pre-description behavior.
+ * alone. A control with no visible label - declared `display.icon_only`, or a
+ * label the bar dropped to keep the button in a tight row - leads with the NAME
+ * on its own line, then the description. Absent description falls back to the
+ * name.
  */
-export declare function actionTooltip(action: Action | undefined, name: string, isDisabled: boolean, reason: string | null | undefined): string;
+export declare function actionTooltip(action: Action | undefined, name: string, isDisabled: boolean, reason: string | null | undefined, 
+/**
+ * True when the button is rendering WITHOUT its label right now - either
+ * because the author declared `display.icon_only`, or because the row ran out
+ * of width and the bar dropped the label to keep the button. Both cases leave
+ * the user looking at an icon, so the tooltip has to say the name first.
+ */
+labelHidden?: boolean): string;
 /**
  * Builds the full dot-qualified action code for API calls.
  */

package/dist-lib/lib/longPressGesture.d.ts

@@ -0,0 +1,55 @@
+/**
+ * How long a press is held before it becomes a Row Menu request. 500ms is what
+ * Android and iOS both use for their own long-press, so a user's thumb already
+ * knows this number.
+ */
+export declare const LONG_PRESS_HOLD_MS = 500;
+/**
+ * How far the pointer may drift and still be a press. Past this the gesture is a
+ * scroll, and a list that opens menus while the user is scrolling it is worse
+ * than one with no long-press at all.
+ */
+export declare const LONG_PRESS_MOVE_TOLERANCE_PX = 10;
+/** Where a press started. `null` means no press is in progress. */
+export type PressOrigin = {
+    x: number;
+    y: number;
+} | null;
+export type LongPressInput = {
+    type: "down";
+    x: number;
+    y: number;
+}
+/** Pointer moved, or the surface under it scrolled. */
+ | {
+    type: "move";
+    x: number;
+    y: number;
+}
+/** Released, cancelled by the OS, or the element lost the pointer. */
+ | {
+    type: "release";
+}
+/** The hold timer elapsed. */
+ | {
+    type: "held";
+};
+export type LongPressOutcome = 
+/** A press is in progress; keep the timer running. */
+"pending"
+/** No press is in progress; cancel any timer. */
+ | "idle"
+/** Open the Row Menu at the press origin. */
+ | "fire";
+export interface LongPressStep {
+    origin: PressOrigin;
+    outcome: LongPressOutcome;
+}
+/**
+ * Advances the gesture. Returns the new origin and what the caller should do.
+ *
+ * A `held` without an origin cannot fire: the timer is cleared on every exit,
+ * but a timer that has already been queued when the press ends would otherwise
+ * open a menu after the user let go.
+ */
+export declare function stepLongPress(origin: PressOrigin, input: LongPressInput, tolerance?: number): LongPressStep;

package/dist-lib/lib/page-inset.d.ts

@@ -0,0 +1,3 @@
+import type { CSSProperties } from "react";
+/** Horizontal padding for a page shell, notch-aware. `base` is the design inset in px. */
+export declare function pageInsetX(base: number): Pick<CSSProperties, "paddingLeft" | "paddingRight">;

package/dist-lib/lib/viewport-category.d.ts

@@ -0,0 +1,44 @@
+export type ViewportCategory = "phone" | "tablet" | "desktop";
+export interface ResponsiveBreakpoints {
+    phoneMax: number;
+    tabletMax: number;
+    /**
+     * The height at or below which a viewport no wider than `tabletMax` is a
+     * phone held sideways. Required, never optional: a missing bound would
+     * silently restore the width-only rule, which is the defect it exists to
+     * remove.
+     */
+    landscapePhoneMaxHeight: number;
+}
+export interface ResponsiveViewport {
+    width: number;
+    height: number;
+    touch?: boolean;
+}
+export interface ResponsiveMode {
+    category: ViewportCategory;
+    width: number;
+    height: number;
+    isPhone: boolean;
+    isTablet: boolean;
+    isDesktop: boolean;
+    touch: boolean;
+}
+export declare const DEFAULT_RESPONSIVE_BREAKPOINTS: ResponsiveBreakpoints;
+/**
+ * The device class, from BOTH viewport axes.
+ *
+ * A phone is a device, not a width. Read from width alone, the same phone is a
+ * phone upright and a tablet on its side - so rotating it swapped cards for a
+ * table, sections for tabs, and the compact header for the desktop one, all at
+ * once. The second clause is that device: no wider than a tablet AND short.
+ *
+ * Height is admitted only UNDER the tablet width ceiling, because a wide short
+ * window (a 1600x480 browser, a wide embed strip) is a desktop, and a height
+ * clause without the ceiling would reclassify it.
+ */
+export declare function resolveViewportCategory(viewport: {
+    width: number;
+    height: number;
+    touch?: boolean;
+}, breakpoints?: ResponsiveBreakpoints): ViewportCategory;