Bug Report: Docs tables scroll horizontally and squeeze columns

Open Beginner friendly
#22,026 2 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
76/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
react, tailwindcss, typescript

Research direction

Start in src/templates/Handbook.tsx, where the table shortcode uses OverflowXSection, and inspect how it sets table width and horizontal overflow. Reproduce the reported wrapping on the Workload identity for GitHub Actions page, then check other docs or handbook tables for the same behavior. Done when tables fill the content column with readable columns and scroll horizontally only when wider than the window.

Written by the indexing model from the issue text.

Description

Report

Markdown tables in docs scroll horizontally, also when the content area has sufficient space. The columns become narrow and the text wraps on almost every word. A right-edge fade shows, so the table looks cut off.

Example: the "Which runs a policy matches" table on Workload identity for GitHub Actions (preview build).

Docs table with horizontal scroll and narrow wrapped columns

Technical info

  • Markdown tables in docs and handbook pages go through OverflowXSection in src/templates/Handbook.tsx (the table shortcode).
  • The issue is possibly not specific to this page. Other docs pages with tables can have the same problem.
  • Browser and device: not known (reported from a screenshot).

Expected outcome, or solution

Tables use the full width of the content column, and the columns have a readable width. Horizontal scroll occurs only when the table is wider than the window.


Created with PostHog from a Slack thread

Dominant language
TypeScript
Stars
1.2k
Forks
952
Avg merge
1d 17h
Merged PRs (30d)
747

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from PostHog/posthog.com

All issues in PostHog/posthog.com

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.