-
Notifications
You must be signed in to change notification settings - Fork 28
Fix table CSS to span full width in documentation #3908
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
|
@copilot the issue is not fixed |
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Fixed in commit 72cfab7. The issue was that Warning Firewall rules blocked me from connecting to one or more addresses (expand for details)I tried to connect to the following addresses, but was blocked by firewall rules:
If you need me to access, download, or install something from one of these locations, you can either:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR fixes table rendering in the documentation by adding CSS rules to make tables span the full content width. The primary change adds width: 100% and table-layout: fixed properties to table elements in both dark and light themes.
Key Changes:
- Added
width: 100%andtable-layout: fixedto.sl-markdown-content tableCSS rules for both dark and light themes - Package-lock.json was updated with peer dependency metadata (appears unrelated to the CSS fix)
Reviewed Changes
Copilot reviewed 1 out of 2 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| docs/src/styles/custom.css | Added width: 100% and table-layout: fixed to table CSS rules in both dark theme (lines 558-559) and light theme (lines 202-203) to make tables span full content width |
| docs/package-lock.json | Updated several dependencies with "peer": true metadata - appears to be an incidental change from npm version differences rather than intentional updates related to the table CSS fix |
Files not reviewed (1)
- docs/package-lock.json: Language not supported
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| "resolved": "https://registry.npmjs.org/@astrojs/starlight/-/starlight-0.35.2.tgz", | ||
| "integrity": "sha512-curGghoW4s5pCbW2tINsJPoxEYPan87ptCOv7GZ+S24N3J6AyaOu/OsjZDEMaIpo3ZlObM5DQn+w7iXl3drDhQ==", | ||
| "license": "MIT", | ||
| "peer": true, |
Copilot
AI
Nov 14, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[nitpick] The changes to package-lock.json appear to be unrelated to the CSS table width fix. Several dependencies have been marked with "peer": true (lines 130, 1823, 1984, 5116, 5628, 6476, 6675), which typically happens when running npm install with a different npm version that better detects peer dependencies.
These changes include packages like @astrojs/starlight, acorn, astro, postcss, rollup, vite, and zod being marked as peer dependencies. While these changes are likely harmless (npm is just better documenting the dependency tree), they should ideally be separated into their own commit or PR since they're not related to the CSS fix.
Consider:
- Reverting these package-lock.json changes if they weren't intentional
- Or, if keeping them, mention them in the PR description as "Updated package-lock.json to reflect peer dependencies more accurately"
| "peer": true, |
| width: 100%; | ||
| table-layout: fixed; |
Copilot
AI
Nov 14, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[nitpick] The table-layout: fixed property has important implications for table rendering that should be considered:
Benefits:
- Forces tables to use the specified width (100% in this case)
- Makes column widths more predictable
- Can improve rendering performance
Potential issues:
- Content that doesn't fit within the calculated column width will overflow or be cut off
- All columns will have equal width by default (unless explicit widths are set on individual columns)
- Long words or URLs without spaces may cause overflow issues
Consider testing this change with:
- Tables containing long URLs or code snippets
- Tables with varying content lengths across columns
- Mobile/narrow viewport widths
If content overflow becomes an issue, you may need to add:
.sl-markdown-content td,
.sl-markdown-content th {
word-wrap: break-word;
overflow-wrap: break-word;
}
Tables in the documentation (e.g., CLI Commands page) were not utilizing the full content area width, appearing cramped and difficult to scan.
Changes
width: 100%andtable-layout: fixedto.sl-markdown-content tableCSS rules for both dark and light themes indocs/src/styles/custom.cssThe
table-layout: fixedproperty is essential to ensure tables properly expand to full width. Without it, tables only expand to fit their content, even whenwidth: 100%is specified.Screenshots
Before:

After:

Tables now properly span the full content width across all documentation pages.
Original prompt
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.