Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Bug] Table hover controls overlap and obscure table content

Open Beginner friendly
#48,823 0 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
65/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
markdown
Domain
frontend

Research direction

Start by reproducing the issue in the Codex App with a conversation containing a Markdown table, then inspect the hover controls that add the expand and copy buttons. Done means both controls remain available without overlapping or obscuring table headers or cell values.

Written by the indexing model from the issue text.

Description

app bug
What version of the Codex App are you using (From “About Codex” dialog)?

26.924.22138

What subscription do you have?

ChatGPT Plus

What platform is your computer?

No response

What issue are you seeing?

After updating the Codex App, hovering over a Markdown table causes the expand and copy buttons to appear in the top-right corner of the table. These floating controls overlap the table content, potentially obscuring column headers and cell values, especially in the rightmost column.

What steps can reproduce the bug?

Open the Codex App.
Open a conversation containing a Markdown table.
Move the mouse cursor over the table.
Observe the expand and copy buttons appearing in the top-right corner.

What is the expected behavior?

The expand and copy buttons should not overlap or obscure any table content. The UI should provide sufficient space for these controls or position them outside the table's content area.

Additional information

No response

Dominant language
Rust
Stars
125k
Forks
19.5k
Avg merge
1m
Merged PRs (30d)
996

Getting set up

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 openai/codex

All issues in openai/codex

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.