@riverbankcms/sdk 0.140.0 → 0.141.0

package/dist/_dts/theme-core/src/buttons/classNames.d.ts

@@ -19,3 +19,19 @@ export declare function themeButtonVariantClassNames(variant: ThemeButtonVariant
 export declare function themeButtonSizeClassName(size: ButtonSizeName): ThemeButtonSizeClassName;
 export declare function themeButtonSelector(variant: ThemeButtonVariantId, size?: ButtonSizeName): string;
 export declare function themeButtonClassName(spec: ThemeButtonClassSpec): ThemeButtonClassName;
+/**
+ * Button classes for an authored button that renders its own trailing icon.
+ *
+ * A separate function rather than a flag on `themeButtonClassName`, because
+ * there is exactly one caller and it should stay visible in a diff. The name
+ * states what the caller knows to be true of its own markup — that it renders a
+ * trailing icon — rather than what the theme does about it. The consequence is
+ * the theme's to decide and to change; a caller naming the consequence would be
+ * asserting a policy it does not own, and would quietly become a lie the moment
+ * that policy moved.
+ *
+ * Do not reach for this to remove an arrow you simply do not want. A trailing
+ * affordance is declared by the button style, and a block overriding that is the
+ * defect this replaced.
+ */
+export declare function themeButtonClassNameWithTrailingIcon(spec: ThemeButtonClassSpec): ThemeButtonClassName;

package/dist/_dts/theme-core/src/buttons/generateButtonCss.d.ts

@@ -1,11 +1,5 @@
 import type { Theme } from '../schema';
 import type { ButtonSystem } from './types';
-/**
- * Class the `button` runtime node adds when it renders its own trailing icon,
- * so a node-level icon suppresses the theme's CSS `::after` affordance.
- * Shared so generator and renderer can't drift.
- */
-export declare const AFFORDANCE_SUPPRESS_CLASS = "rb-affordance-off";
 export interface GenerateButtonCssOptions {
     themeId: string;
     theme: Theme;

package/dist/_dts/theme-core/src/buttons/resolvedButtonCss.d.ts

@@ -11,9 +11,9 @@ export declare function resolvedButtonColourDeclarations(colour: ResolvedButtonC
 }>): readonly ButtonCssDeclaration[];
 export declare function resolvedButtonFocusDeclarations(indicator: ResolvedButtonFocusIndicator, role?: string): readonly ButtonCssDeclaration[];
 /**
- * Disabled buttons retain their validated colour pair and add a non-layout
- * visual affordance. `currentColor` keeps the cue inside the same contrast
- * relationship, while retaining pointer events lets the not-allowed cursor
- * remain observable.
+ * Disabled buttons are deliberately muted as unavailable controls. Native
+ * disabled controls are exempt from active-control contrast requirements;
+ * opacity distinguishes the state without introducing a focus-like outline.
+ * Retaining pointer events lets the not-allowed cursor remain observable.
  */
 export declare const RESOLVED_BUTTON_DISABLED_DECLARATIONS: readonly ButtonCssDeclaration[];