payloadcms / payloadcms/payload

Weird Validation error tooltip text clipping

Open
#16,774 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area: ui created-by: Contributor status: needs-triage v3
Dominant language
TypeScript
Stars
44.8k
Forks
4.2k
Avg merge
2d 21h
Merged PRs (30d)
53

Description

Describe the Bug.

"Can you tell is this Q or G ? q or g ?"

Image

Not sure if this Windows specific, but still confusing.

Reproduction Steps

Create custom validation function where you return "q and g" symbols.

Environment Info
Binaries:
  Node: 25.8.1
  npm: N/A
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  payload: 3.82.1
  next: 16.2.3
  @payloadcms/db-mongodb: 3.82.1
  @payloadcms/email-nodemailer: 3.82.1
  @payloadcms/graphql: 3.82.1
  @payloadcms/live-preview: 3.82.1
  @payloadcms/live-preview-react: 3.82.1
  @payloadcms/next/utilities: 3.82.1
  @payloadcms/plugin-multi-tenant: 3.82.1
  @payloadcms/plugin-nested-docs: 3.82.1
  @payloadcms/plugin-search: 3.82.1
  @payloadcms/plugin-seo: 3.82.1
  @payloadcms/richtext-lexical: 3.82.1
  @payloadcms/translations: 3.82.1
  @payloadcms/ui/shared: 3.82.1
  react: 19.2.3
  react-dom: 19.2.3
Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 11 Pro
  Available memory (MB): 31861
  Available CPU cores: 16

Contributor guide

Open the 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.

Research direction

Reproduce the custom validation tooltip in the Payload admin UI on Windows 11 using a validator that returns text containing q and g symbols. Start by locating the validation error tooltip implementation and its styling; done means the complete message is visible without clipping in the reported environment.

Written by the indexing model from the issue text.

Assessment

Tech stack
next.js, react, typescript
Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.