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

[Bug] UI: Share and Copy icons are in the wrong order next to the timestamp

Open Beginner friendly
  • Is something wrong?
#16,423 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
72/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
typescript
Domain
frontend

Research direction

Start in the apps/web area and locate the chat-history message UI that renders the timestamp and its Share and Copy icons. Confirm the current order, then check the interface to verify that Copy appears on the left and Share on the right.

Written by the indexing model from the issue text.

Description

bug needs-triage
Before submitting
  • I searched existing issues and did not find a duplicate.
  • I included enough detail to reproduce or investigate the problem.
Area

apps/web

Steps to reproduce

Open the T3 Code interface.
Locate any message in the chat history.
Hover over or look at the timestamp (e.g., "2:55 PM") next to the message.
Observe the order of the icons: [Share Icon] [Copy Icon].

Expected behavior

The "Copy" icon should be on the left, and the "Share" icon should be on the right. So the order should be: [Copy Icon] [Share Icon].

Actual behavior

The "Share" icon is on the left, and the "Copy" icon is on the right. The order is: [Share Icon] [Copy Icon].

Impact

Cosmetic issue

Version or commit

No response

Environment

macOS 27.1

Logs or stack traces
Screenshots, recordings, or supporting files

image.png

Workaround

No response

Dominant language
TypeScript
Stars
24.8k
Forks
6.4k
Avg merge
7h 58m
Merged PRs (30d)
258

Getting set up

Open in Codespaces

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

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 pingdotgg/t3code

All issues in pingdotgg/t3code

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.