@flytedan/flytebot-design-system 0.55.0 → 0.55.2

package/dist/index.d.cts

@@ -397,7 +397,8 @@ declare function ScreenHead({ kicker, title, lede, actions }: ScreenHeadProps):
  * `@container` query — the grid element already sizes itself off its parent, the same as any
  * other block box. `--card-grid-min` (default 280px) is the floor a card may shrink to before
  * a track drops; two 280px cards plus the gap don't fit in a 375px-wide content column, so
- * that width is always exactly one column, and a typical ~1280px desktop content column fits
+ * that width is always exactly one column (a `minCardWidth` wider than the container clamps to
+ * the container: the track floor is `min(100%, var(--card-grid-min))`, MP-299), and a typical ~1280px desktop content column fits
  * four (see CardGrid.browser.test.tsx for the measured counts this rests on, including the
  * container-vs-viewport regression case added under review comment 2920 finding 1: a fixed-
  * width container nested inside a differently-sized real viewport still shows the container's
@@ -437,7 +438,8 @@ interface CardGridProps {
     children?: React.ReactNode;
     /** The width, in px, a card may shrink to before a column drops. Default 280 is tuned so a
      *  375px-wide content column (a phone) is always exactly one column and a ~1280px desktop
-     *  content column fits four — see the file doc comment. */
+     *  content column fits four — see the file doc comment. A value wider than the container
+     *  collapses to one full-width column rather than overflowing it. */
     minCardWidth?: number;
     /** One of the spacing scale's named tiers (styles/tokens.css's `--s-*`), same vocabulary as
      *  `fd-gap-*` (SMS-7). Applies to both the row and column gap. */

package/dist/index.d.ts

@@ -397,7 +397,8 @@ declare function ScreenHead({ kicker, title, lede, actions }: ScreenHeadProps):
  * `@container` query — the grid element already sizes itself off its parent, the same as any
  * other block box. `--card-grid-min` (default 280px) is the floor a card may shrink to before
  * a track drops; two 280px cards plus the gap don't fit in a 375px-wide content column, so
- * that width is always exactly one column, and a typical ~1280px desktop content column fits
+ * that width is always exactly one column (a `minCardWidth` wider than the container clamps to
+ * the container: the track floor is `min(100%, var(--card-grid-min))`, MP-299), and a typical ~1280px desktop content column fits
  * four (see CardGrid.browser.test.tsx for the measured counts this rests on, including the
  * container-vs-viewport regression case added under review comment 2920 finding 1: a fixed-
  * width container nested inside a differently-sized real viewport still shows the container's
@@ -437,7 +438,8 @@ interface CardGridProps {
     children?: React.ReactNode;
     /** The width, in px, a card may shrink to before a column drops. Default 280 is tuned so a
      *  375px-wide content column (a phone) is always exactly one column and a ~1280px desktop
-     *  content column fits four — see the file doc comment. */
+     *  content column fits four — see the file doc comment. A value wider than the container
+     *  collapses to one full-width column rather than overflowing it. */
     minCardWidth?: number;
     /** One of the spacing scale's named tiers (styles/tokens.css's `--s-*`), same vocabulary as
      *  `fd-gap-*` (SMS-7). Applies to both the row and column gap. */

package/dist/index.js

@@ -1598,6 +1598,9 @@ function AppShell({
                 style: {
                   flex: 1,
                   minWidth: 0,
+                  // MP-298: positioned so absolutely positioned content inside (a chart's `.fd-sr` data
+                  // table) is contained and clipped by this scroller, never stretching the document.
+                  position: "relative",
                   overflowY: "auto",
                   padding: 24,
                   maxWidth: contentMaxWidth,