@besaitech/ng-design-system 0.0.75 → 0.0.76

package/index.d.ts

@@ -1686,25 +1686,26 @@ declare class SdsBulkBar {
     static ɵcmp: _angular_core.ɵɵComponentDeclaration<SdsBulkBar, "sds-bulk-bar", never, { "count": { "alias": "count"; "required": false; "isSignal": true; }; "countLabel": { "alias": "countLabel"; "required": false; "isSignal": true; }; "clearLabel": { "alias": "clearLabel"; "required": false; "isSignal": true; }; "ariaLabel": { "alias": "ariaLabel"; "required": false; "isSignal": true; }; "position": { "alias": "position"; "required": false; "isSignal": true; }; }, { "clear": "clear"; }, never, ["*"], true, never>;
 }
 
-/** Whether the bar pins to the bottom of the scroll container (default) or sits in flow. */
+/** Whether the bar floats at the bottom of the scroll container (default) or sits in flow. */
 type SdsFormActionsPosition = 'sticky' | 'static';
 /**
  * The action bar at the foot of a form: Cancel, Save, and whatever commits the thing — projected as
- * buttons, right-aligned, on a bordered strip that pins to the bottom of the scroll container so the
- * save button stays in reach on a long editor.
+ * buttons on a floating card that rides at the bottom of the scroll container, so the save button
+ * stays in reach on a long editor.
  *
  * Project a destructive or secondary action with `sdsFormActionsStart` and it is pushed to the left,
  * away from the confirming buttons, which is the point: Delete should not sit a few pixels from Save.
  *
- * Not {@link SdsBulkBar}, which is for a selection: that one hides itself at zero, says "N selected",
- * carries a clear-selection button and is announced as a toolbar. A form footer is none of those, and
- * dressing one up as the other costs a fake count and a screen reader that announces a save bar as
- * bulk actions. This is a plain labelled `role="group"` — not a toolbar, because the buttons belong in
- * the form's normal tab order and a toolbar role tells a screen-reader user to expect arrow keys.
+ * Deliberately the same chrome as {@link SdsBulkBar} — rounded card, full border, solid surface,
+ * `shadow-xl`, floating clear of the bottom edge rather than welded to it, same entrance. The two are
+ * the app's only bars that hover over scrolling content, and a form footer that looked like a
+ * different species from the bulk bar would read as a different kind of thing. What they are not is
+ * the same semantics: that one is a `role="toolbar"` for a selection, announcing "N selected" and
+ * hiding itself at zero. This is a plain labelled `role="group"`, because these buttons belong in the
+ * form's normal tab order and a toolbar role tells a screen-reader user to expect arrow keys.
  *
- * The bar spans its container and carries its own horizontal padding. To let it bleed past a padded
- * container's edge, put the matching negative margin on the host — the host is a block element:
- * `<sds-form-actions class="-mx-4 md:-mx-6">`.
+ * It floats, so do not bleed it past its container with negative margins the way a flush strip wants:
+ * the rounded corners and the shadow need the inset to read as a card.
  *
  * @example
  * <sds-form-actions>

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@besaitech/ng-design-system",
-  "version": "0.0.75",
+  "version": "0.0.76",
   "publishConfig": {
     "registry": "https://registry.npmjs.org/",
     "access": "public"