bad default styling

[paddymul]

Checks

• I have checked that this issue has not already been reported.

• I have confirmed this bug exists on the latest version of Buckaroo.

What type of jupyter notebook were you using (VSCode notebook, google colab, Jupyter Lab, Jupyter notebook). Select multiple if you can reproduce this in multiple environments. If other, please add to description.

Other (please describe in Issue Description)

Reproducible example

Issue description

columns with short columns have hidden data. the autosizing should do a better job of this. I think we have summary stats about the number of signficant digits. if not they are trivial to add. we should never have the ...

disregard the coloring in this picture.

Expected behavior

all of the signficant digts should be visible. if the values are very large. include abbreviations $3m , 5.7B ...

Installed versions

Details

``` Replace this line with the output of buckaroo.debug_packages(). Leave the backticks in place. ```

n/a

Jupyter Log output

[paddymul]

Implementation plan for this issue:

1. Add deterministic column width policy in JS (applies to all table views)

• Implement width policy logic in packages/buckaroo-js-core/src/components/DFViewerParts/gridUtils.ts.
• Apply from packages/buckaroo-js-core/src/components/DFViewerParts/DFViewerInfinite.tsx so every DFViewer/Buckaroo table path gets the same behavior.

2. Compute preferred pixel width by inspecting column data/metadata

• Use existing column type/formatter context and summary stats to estimate displayed string lengths.
• Convert estimate to explicit pixel widths (width / minWidth) on column defs.
• Reserve histogram renderer minimum width of 110px.

3. Protect pinned/index columns first

• During contention, keep left/index pinned columns stable before shrinking other columns.

4. Prioritize numeric columns over text when shrinking

• If total preferred widths exceed viewport:
  • Shrink non-numeric/text columns first.
  • Preserve numeric column width as long as possible.
• Rationale: text truncation is regrettable, but numeric truncation is more harmful for table analysis.

5. Use explicit width allocation instead of relying solely on autosize

• Keep autosize as a helper where useful, but final behavior should come from explicit width policy.
• Recompute on:
  • first data render
  • display/schema changes
  • container resize

6. Add tests

• Extend packages/buckaroo-js-core/src/components/DFViewerParts/gridUtils.test.ts to cover:
  • histogram min width (110)
  • pinned/index protection
  • numeric-over-text contention behavior
  • preferred-width-without-contention behavior

Related follow-ups (separate issues/PRs):

• Add opt-in compact numeric formatter (3M, 5.7B) with full-value tooltip #597: opt-in compact numeric formatter (3M, 5.7B) with full-value tooltip
• Follow-up: column width contention policy and toggleable style presets #596: width contention presets / style preset toggle work

[paddymul]

Implementation Plan

Overview

Investigate and fix the default styling regression.

Steps

1. Reproduce — create a minimal notebook with a basic DataFrame, render with BuckarooWidget, screenshot the output. Compare against expected styling from the last known-good release.

2. Bisect — check recent commits that touched styling/CSS/AG Grid config:

   • Fix left-pinned index column for summary stats #587 (left-pinned index column) is a likely candidate
   • Check AG Grid theme CSS, column definitions, and default column_config_overrides

3. Identify root cause — likely one of:

   • Missing/wrong AG Grid theme class
   • Column width defaults changed
   • CSS specificity issue from recent changes
   • Pinned column config affecting non-pinned columns

4. Fix — restore correct defaults while preserving the intentional changes from recent PRs.

5. Test — add a Playwright visual regression test or screenshot comparison for default widget rendering.

Files to investigate

• packages/buckaroo-js-core/src/components/DFViewerParts/ — AG Grid config
• CSS/theme files
• Recent commits touching column definitions

@codex

[chatgpt-codex-connector]

Summary

• Added a deterministic column width policy and wired it into dfToAgrid so generated AG Grid column defs now receive explicit width/minWidth, including nested children. This restores stable default sizing instead of relying solely on AG Grid autosizing. packages/buckaroo-js-core/src/components/DFViewerParts/gridUtils.tsL246-L300
• Implemented width heuristics and contention handling rules:
  • histogram columns get a hard minimum of 110px,
  • numeric columns get a stronger minimum than text,
  • shrink order is non-pinned text → non-pinned numeric → pinned columns (protecting pinned/index first). packages/buckaroo-js-core/src/components/DFViewerParts/gridUtils.tsL302-L392
• Added focused tests for the new policy: histogram min width, pinned/index protection, numeric-vs-text contention behavior, and preferred-width behavior when there is no contention. packages/buckaroo-js-core/src/components/DFViewerParts/gridUtils.test.tsL197-L264
• Committed changes on branch in commit e6488e6 and created the follow-up PR via make_pr with title: “Fix default DFViewer column sizing regression on top of #bad-default-styling”.

Testing

• ✅ npm test -- --runInBand src/components/DFViewerParts/gridUtils.test.ts (run in packages/buckaroo-js-core)

View task →

[paddymul]

Related: PRs #545, #587, #590

Recent PRs that touched styling:

• PR fix: summary stats inherit alignment for count and freq rows #545 (merged): Summary stats inherit alignment for count and freq rows
• PR Fix left-pinned index column for summary stats #587 (merged): Fix left-pinned index column for summary stats readability
• PR fix: Playwright row count off-by-one with pinned columns #590 (merged): Fix Playwright row count off-by-one with pinned columns

These may have caused the styling regression or may have partially addressed it. Worth checking if this issue still reproduces on the latest release (0.12.13).