Skip to content

Fix timings table footer column count when custom timings exist#697

Open
leno23 wants to merge 1 commit into
MiniProfiler:mainfrom
leno23:fix/timings-table-tfoot-columns-687
Open

Fix timings table footer column count when custom timings exist#697
leno23 wants to merge 1 commit into
MiniProfiler:mainfrom
leno23:fix/timings-table-tfoot-columns-687

Conversation

@leno23
Copy link
Copy Markdown

@leno23 leno23 commented May 25, 2026

Summary

  • Fixes a browser warning when MiniProfiler renders profiles with CustomTimingStats (for example SQL timings).
  • The timings table header adds one column per custom timing type, but the footer row only spanned the fixed five base columns.
  • Adds matching empty footer cells so header/body/footer column counts stay aligned.

Fixes #687

Test plan

  • Build MiniProfiler.Shared (TypeScript compile + bundle)
  • Open a profile result that includes custom timings (e.g. SQL)
  • Confirm the browser console no longer reports: "A table row was 5 columns wide, which is less than the column count established by the first row"

Made with Cursor

The timings table header adds dynamic columns for CustomTimingStats,
but the footer row always spanned only five columns. Browsers then warn
that the footer row is narrower than the header row.

Add matching empty footer cells for each custom timing column.

Fixes MiniProfiler#687

Co-authored-by: Cursor <cursoragent@cursor.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

MiniProfiler.ts: 'A table row was 5 columns wide, which is less than the column count established by the first row'

1 participant