@allxsmith/bestax-bulma 5.16.8 → 5.16.10

package/dist/types/components/Avatar.d.ts

@@ -18,7 +18,14 @@ export interface AvatarOwnProps extends Omit<BulmaClassesProps, 'color'> {
     className?: string;
     /** Image URL. On load error (or if absent), falls back to initials, then `icon`. */
     src?: string;
-    /** Alternate text for the image (used for the accessible name in every render mode). An explicit `alt=""` marks a non-interactive avatar as decorative. */
+    /**
+     * Alternate text for the image (used for the accessible name in every render mode). An
+     * explicit `alt=""` marks a non-interactive avatar as decorative.
+     *
+     * A link or button avatar is never decorative — it keeps an accessible name — and a custom
+     * component passed to `as` counts as one unless it states otherwise, so `alt=""` on a custom
+     * wrapper needs that signal alongside it. `as` documents which props carry it.
+     */
     alt?: string;
     /** Derives initials and a deterministic background color when no `src` is shown. */
     name?: string;
@@ -80,7 +87,23 @@ type AvatarForwardedProp = 'href' | 'target' | 'rel';
  * @extraProp {PolymorphicRef<React.ElementType>} [ref] - Ref forwarded to the element `as` renders, typed from `as`: the DOM node for an intrinsic tag, or whatever handle a custom component exposes.
  */
 export type AvatarProps<T extends React.ElementType = 'figure'> = Omit<AvatarOwnProps, Extract<AvatarForwardedProp, keyof React.ComponentPropsWithoutRef<T>>> & Omit<React.ComponentPropsWithoutRef<T>, Exclude<keyof AvatarOwnProps, AvatarForwardedProp> | 'as'> & {
-    /** Element/component to render as. Defaults to `'a'` when `href` is set, else `'figure'`. */
+    /**
+     * Element/component to render as. Defaults to `'a'` when `href` is set, else `'figure'`.
+     *
+     * This also decides whether the avatar is treated as interactive, which is what keeps
+     * `role="img"` and the `alt=""` decorative opt-out off a link or button. A custom
+     * component counts — a router link takes `to` rather than this component's `href`, so
+     * its own props cannot say — while `'a'`, `'button'`, and a custom element given an
+     * `href` count for the reason they read.
+     *
+     * If your custom component renders something that really is just a picture, say so with
+     * `role="img"` and it is treated as one, `alt=""` included. A truthy `aria-hidden` says it
+     * too, and so do `role="presentation"` and `role="none"` — though ARIA's own conflict
+     * resolution drops those two whenever the avatar still carries a name, so prefer
+     * `role="img"`. A role claiming the opposite, such as `"button"`, says nothing here, and
+     * neither does an `href`: that settles it on its own. A genuine `'a'`/`'button'`/`href`
+     * avatar keeps its accessible name either way.
+     */
     as?: T;
 };
 /**

package/dist/types/components/Card.d.ts

@@ -160,7 +160,3 @@ export declare const Card: React.FC<CardProps> & {
     Footer: React.FC<CardFooterProps>;
     FooterItem: React.FC<CardFooterItemProps>;
 };
-/** Internal test-only exports. Not part of the public API. */
-export declare const __test_exports__: {
-    renderFooter: (footer: CardProps["footer"], classPrefix: string | undefined) => React.JSX.Element[] | null;
-};

package/dist/types/components/Dropdown.d.ts

@@ -3,6 +3,9 @@ import { BulmaClassesProps } from '../helpers/useBulmaClasses.js';
 import type { ConstrainedPolymorphicComponentWithoutRef } from '../helpers/polymorphic.js';
 /**
  * Checks if code is running in a browser environment.
+ * @deprecated Dropdown's internal SSR guard, exported by accident; it will
+ * be removed in the next major. Check `typeof window !== 'undefined' &&
+ * typeof document !== 'undefined'` instead.
  * @param win - Window object.
  * @param doc - Document object.
  * @returns {boolean} True if in browser, false otherwise.

package/dist/types/components/Navbar.d.ts

@@ -106,7 +106,11 @@ export interface NavbarBurgerProps extends React.ButtonHTMLAttributes<HTMLButton
     color?: 'primary' | 'link' | 'info' | 'success' | 'warning' | 'danger';
     /** Whether the burger is active. */
     active?: boolean;
-    /** Custom content inside the burger. */
+    /**
+     * Custom content inside the burger, rendered after its four bar spans.
+     * Bulma styles every `<span>` in the burger as a bar, so an extra span here
+     * draws an extra bar.
+     */
     children?: React.ReactNode;
     /** Aria label for accessibility. */
     'aria-label'?: string;
@@ -217,7 +221,20 @@ export interface NavbarLinkOwnProps extends Omit<BulmaClassesProps, 'color' | 'b
  * @extraProp {PolymorphicRef<React.ElementType>} [ref] - Ref forwarded to the element `as` renders, typed from `as`: the DOM node for an intrinsic tag, or whatever handle a custom component exposes.
  */
 export type NavbarLinkProps<T extends React.ElementType = 'a'> = NavbarLinkOwnProps & Omit<React.ComponentPropsWithoutRef<T>, keyof NavbarLinkOwnProps | 'as'> & {
-    /** Render as another intrinsic element (`'button'`, `'span'`) or a custom component. Defaults to `'a'`. */
+    /**
+     * Render as another intrinsic element (`'button'`, `'span'`) or a custom component. Defaults to `'a'`.
+     *
+     * Inside a `Navbar.Dropdown` this also decides the trigger's semantics. A custom
+     * component is taken to be interactive already — a router link, typically — so it
+     * keeps its own role and click behaviour. An intrinsic tag is judged on what it is:
+     * `'button'`, or anything carrying an `href`, is left alone, and everything else
+     * (`'span'`, a bare `'a'`, a custom element) gets `role="button"`, `tabIndex` and a
+     * click that opens the dropdown.
+     *
+     * If your custom component renders something non-interactive, pass `role="button"` and
+     * it takes that fallback too — `tabIndex` and click included. The keyboard path is
+     * attached either way.
+     */
     as?: T;
 };
 /**

package/dist/types/components/Toast.d.ts

@@ -16,7 +16,11 @@ export interface ToastProps extends Omit<React.HTMLAttributes<HTMLDivElement>, '
     type?: ToastType;
     /** Color variant — colors the **action button** text. */
     actionType?: ToastType;
-    /** Position on the screen. Default: 'top-right'. */
+    /**
+     * Position on the screen. Default: 'top-right'. On a standalone `<Toast>`
+     * this places it; through `toast.show()` it is currently ignored, because
+     * `ToastContainer`'s own `position` places every toast it shows.
+     */
     position?: ToastPosition;
     /** Duration in ms before auto-close. `0` disables auto-close. */
     duration?: number;

package/dist/types/elements/Notification.d.ts

@@ -58,7 +58,10 @@ export interface NotificationOptions {
     isLight?: boolean;
     /** Duration in ms before auto-close. Default 3000. */
     duration?: number;
-    /** Position on the screen. Default 'top-right'. */
+    /**
+     * Position on the screen. Currently ignored: `NotificationContainer`'s own
+     * `position` places every notification it shows, so set it there.
+     */
     position?: NotificationPosition;
     /** When true, notifications enter a FIFO queue and display one at a time. Default false. */
     queue?: boolean;
@@ -136,7 +139,9 @@ export declare const notification: {
 };
 /**
  * Container component for rendering programmatic notifications.
- * Place once at your app root to enable the notification API.
+ * Place once at your app root to enable the notification API. Mount it
+ * before calling `notification`: a notification shown while no container is
+ * mounted doesn't appear when one mounts, only alongside the next call.
  *
  * @function
  * @param {{ position?: NotificationPosition }} props - Container props.

package/dist/types/form/File.d.ts

@@ -29,9 +29,16 @@ export interface FileProps extends Omit<React.InputHTMLAttributes<HTMLInputEleme
     hasName?: boolean;
     /** Text on the file CTA button (defaults to "Choose a file…"). */
     buttonLabel?: React.ReactNode;
-    /** Left icon element. */
+    /**
+     * Left icon element. It renders inside the `<label>` that names the file input, beside
+     * `buttonLabel`, so pass an `Icon` with `aria-hidden` (`<Icon name="upload" aria-hidden="true" />`);
+     * otherwise its default `aria-label="icon"` becomes part of the input's accessible name.
+     */
     iconLeft?: React.ReactNode;
-    /** Right icon element. */
+    /**
+     * Right icon element. Sits inside the same `<label>` as `iconLeft`, so the same applies:
+     * give an `Icon` here `aria-hidden`, or "icon" joins the input's accessible name.
+     */
     iconRight?: React.ReactNode;
     /** Additional CSS classes to apply. */
     className?: string;

package/dist/types-cjs/components/Avatar.d.ts

@@ -18,7 +18,14 @@ export interface AvatarOwnProps extends Omit<BulmaClassesProps, 'color'> {
     className?: string;
     /** Image URL. On load error (or if absent), falls back to initials, then `icon`. */
     src?: string;
-    /** Alternate text for the image (used for the accessible name in every render mode). An explicit `alt=""` marks a non-interactive avatar as decorative. */
+    /**
+     * Alternate text for the image (used for the accessible name in every render mode). An
+     * explicit `alt=""` marks a non-interactive avatar as decorative.
+     *
+     * A link or button avatar is never decorative — it keeps an accessible name — and a custom
+     * component passed to `as` counts as one unless it states otherwise, so `alt=""` on a custom
+     * wrapper needs that signal alongside it. `as` documents which props carry it.
+     */
     alt?: string;
     /** Derives initials and a deterministic background color when no `src` is shown. */
     name?: string;
@@ -80,7 +87,23 @@ type AvatarForwardedProp = 'href' | 'target' | 'rel';
  * @extraProp {PolymorphicRef<React.ElementType>} [ref] - Ref forwarded to the element `as` renders, typed from `as`: the DOM node for an intrinsic tag, or whatever handle a custom component exposes.
  */
 export type AvatarProps<T extends React.ElementType = 'figure'> = Omit<AvatarOwnProps, Extract<AvatarForwardedProp, keyof React.ComponentPropsWithoutRef<T>>> & Omit<React.ComponentPropsWithoutRef<T>, Exclude<keyof AvatarOwnProps, AvatarForwardedProp> | 'as'> & {
-    /** Element/component to render as. Defaults to `'a'` when `href` is set, else `'figure'`. */
+    /**
+     * Element/component to render as. Defaults to `'a'` when `href` is set, else `'figure'`.
+     *
+     * This also decides whether the avatar is treated as interactive, which is what keeps
+     * `role="img"` and the `alt=""` decorative opt-out off a link or button. A custom
+     * component counts — a router link takes `to` rather than this component's `href`, so
+     * its own props cannot say — while `'a'`, `'button'`, and a custom element given an
+     * `href` count for the reason they read.
+     *
+     * If your custom component renders something that really is just a picture, say so with
+     * `role="img"` and it is treated as one, `alt=""` included. A truthy `aria-hidden` says it
+     * too, and so do `role="presentation"` and `role="none"` — though ARIA's own conflict
+     * resolution drops those two whenever the avatar still carries a name, so prefer
+     * `role="img"`. A role claiming the opposite, such as `"button"`, says nothing here, and
+     * neither does an `href`: that settles it on its own. A genuine `'a'`/`'button'`/`href`
+     * avatar keeps its accessible name either way.
+     */
     as?: T;
 };
 /**

package/dist/types-cjs/components/Card.d.ts

@@ -160,7 +160,3 @@ export declare const Card: React.FC<CardProps> & {
     Footer: React.FC<CardFooterProps>;
     FooterItem: React.FC<CardFooterItemProps>;
 };
-/** Internal test-only exports. Not part of the public API. */
-export declare const __test_exports__: {
-    renderFooter: (footer: CardProps["footer"], classPrefix: string | undefined) => React.JSX.Element[] | null;
-};

package/dist/types-cjs/components/Dropdown.d.ts

@@ -3,6 +3,9 @@ import { BulmaClassesProps } from '../helpers/useBulmaClasses.js';
 import type { ConstrainedPolymorphicComponentWithoutRef } from '../helpers/polymorphic.js';
 /**
  * Checks if code is running in a browser environment.
+ * @deprecated Dropdown's internal SSR guard, exported by accident; it will
+ * be removed in the next major. Check `typeof window !== 'undefined' &&
+ * typeof document !== 'undefined'` instead.
  * @param win - Window object.
  * @param doc - Document object.
  * @returns {boolean} True if in browser, false otherwise.

package/dist/types-cjs/components/Navbar.d.ts

@@ -106,7 +106,11 @@ export interface NavbarBurgerProps extends React.ButtonHTMLAttributes<HTMLButton
     color?: 'primary' | 'link' | 'info' | 'success' | 'warning' | 'danger';
     /** Whether the burger is active. */
     active?: boolean;
-    /** Custom content inside the burger. */
+    /**
+     * Custom content inside the burger, rendered after its four bar spans.
+     * Bulma styles every `<span>` in the burger as a bar, so an extra span here
+     * draws an extra bar.
+     */
     children?: React.ReactNode;
     /** Aria label for accessibility. */
     'aria-label'?: string;
@@ -217,7 +221,20 @@ export interface NavbarLinkOwnProps extends Omit<BulmaClassesProps, 'color' | 'b
  * @extraProp {PolymorphicRef<React.ElementType>} [ref] - Ref forwarded to the element `as` renders, typed from `as`: the DOM node for an intrinsic tag, or whatever handle a custom component exposes.
  */
 export type NavbarLinkProps<T extends React.ElementType = 'a'> = NavbarLinkOwnProps & Omit<React.ComponentPropsWithoutRef<T>, keyof NavbarLinkOwnProps | 'as'> & {
-    /** Render as another intrinsic element (`'button'`, `'span'`) or a custom component. Defaults to `'a'`. */
+    /**
+     * Render as another intrinsic element (`'button'`, `'span'`) or a custom component. Defaults to `'a'`.
+     *
+     * Inside a `Navbar.Dropdown` this also decides the trigger's semantics. A custom
+     * component is taken to be interactive already — a router link, typically — so it
+     * keeps its own role and click behaviour. An intrinsic tag is judged on what it is:
+     * `'button'`, or anything carrying an `href`, is left alone, and everything else
+     * (`'span'`, a bare `'a'`, a custom element) gets `role="button"`, `tabIndex` and a
+     * click that opens the dropdown.
+     *
+     * If your custom component renders something non-interactive, pass `role="button"` and
+     * it takes that fallback too — `tabIndex` and click included. The keyboard path is
+     * attached either way.
+     */
     as?: T;
 };
 /**

package/dist/types-cjs/components/Toast.d.ts

@@ -16,7 +16,11 @@ export interface ToastProps extends Omit<React.HTMLAttributes<HTMLDivElement>, '
     type?: ToastType;
     /** Color variant — colors the **action button** text. */
     actionType?: ToastType;
-    /** Position on the screen. Default: 'top-right'. */
+    /**
+     * Position on the screen. Default: 'top-right'. On a standalone `<Toast>`
+     * this places it; through `toast.show()` it is currently ignored, because
+     * `ToastContainer`'s own `position` places every toast it shows.
+     */
     position?: ToastPosition;
     /** Duration in ms before auto-close. `0` disables auto-close. */
     duration?: number;

package/dist/types-cjs/elements/Notification.d.ts

@@ -58,7 +58,10 @@ export interface NotificationOptions {
     isLight?: boolean;
     /** Duration in ms before auto-close. Default 3000. */
     duration?: number;
-    /** Position on the screen. Default 'top-right'. */
+    /**
+     * Position on the screen. Currently ignored: `NotificationContainer`'s own
+     * `position` places every notification it shows, so set it there.
+     */
     position?: NotificationPosition;
     /** When true, notifications enter a FIFO queue and display one at a time. Default false. */
     queue?: boolean;
@@ -136,7 +139,9 @@ export declare const notification: {
 };
 /**
  * Container component for rendering programmatic notifications.
- * Place once at your app root to enable the notification API.
+ * Place once at your app root to enable the notification API. Mount it
+ * before calling `notification`: a notification shown while no container is
+ * mounted doesn't appear when one mounts, only alongside the next call.
  *
  * @function
  * @param {{ position?: NotificationPosition }} props - Container props.

package/dist/types-cjs/form/File.d.ts

@@ -29,9 +29,16 @@ export interface FileProps extends Omit<React.InputHTMLAttributes<HTMLInputEleme
     hasName?: boolean;
     /** Text on the file CTA button (defaults to "Choose a file…"). */
     buttonLabel?: React.ReactNode;
-    /** Left icon element. */
+    /**
+     * Left icon element. It renders inside the `<label>` that names the file input, beside
+     * `buttonLabel`, so pass an `Icon` with `aria-hidden` (`<Icon name="upload" aria-hidden="true" />`);
+     * otherwise its default `aria-label="icon"` becomes part of the input's accessible name.
+     */
     iconLeft?: React.ReactNode;
-    /** Right icon element. */
+    /**
+     * Right icon element. Sits inside the same `<label>` as `iconLeft`, so the same applies:
+     * give an `Icon` here `aria-hidden`, or "icon" joins the input's accessible name.
+     */
     iconRight?: React.ReactNode;
     /** Additional CSS classes to apply. */
     className?: string;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@allxsmith/bestax-bulma",
-  "version": "5.16.8",
+  "version": "5.16.10",
   "description": "A fully-typed React component library for the Bulma CSS framework. Build modern UIs quickly with reusable, accessible, and customizable Bulma-based React components.",
   "main": "dist/index.cjs",
   "module": "dist/index.esm.js",