Skip to content

Wrap long Atlas claim labels on narrow screens - #20

Merged
Maverick0351a merged 1 commit into
mainfrom
codex/atlas-mobile-containment
Oct 21, 2026
Merged

Maverick0351a merged 1 commit into
mainfrom
codex/atlas-mobile-containment

Conversation

@Maverick0351a

Copy link
Copy Markdown
Owner

At a 390px viewport, the Atlas claim inspector lets a long comparison ID force the page to 534px scroll width despite a 376px client width, even with disclosures closed. Allow claim summaries and table captions to wrap anywhere so the complete identifiers can fit their available width. The graph keeps its intentional internal scroller.

Evidence

  • Public repro: carrier 4, shape T06, entry n4-E16457, collapsed and expanded claim panels. The overflow was measured inside the Atlas iframe, separately from the Hugging Face wrapper.
  • The baseline stylesheet fails the new source contract. Repaired source checks all 39 entries / 234 complete labels, ten rejection controls and two property-case positive controls.
  • Existing UI checks pass: 518 grouping cases, 304 rejection witnesses, 115 filter combinations, 282 selection assertions and 224 color pairings.
  • Contributor checks pass: python -m unittest discover -v (33 tests), python run_experiment.py --out runs/atlas-mobile-validation-20261020T223143Z, and evidence verification/comparison. The 143,685-candidate reproduction has no mathematical differences from recorded evidence.
  • The source contract runs through the existing selection checker. It does not emulate layout; the same public-browser repro remains required after deployment.
  • Initial independent review found three mixed-case CSS-property false passes in the checker. Ordinary property names now normalize ASCII case, custom names preserve case, and the original failed controls are retained in the review evidence.
  • Independent follow-up reproduces the old three failures; the repaired checker passes all 22 independent cases and four targeted property/custom-case controls. Exact source and unchanged dependencies were separately bound.

Scope

CSS wrapping, a focused checker and its existing-checker hookup, and a bounded work-log entry. Data, mathematical claims, renderer, downloads and CI workflow are unchanged. Substantial AI assistance: Codex author and independent AI-assisted review; no external peer-review claim.

  • I checked the contribution guide and claim boundaries.
  • Relevant tests and reproduction checks pass, or remaining failures are explained above.
  • Documentation and generated evidence agree with the change.

@qodo-code-review

Copy link
Copy Markdown

Qodo reviews are paused for this user.

Troubleshooting steps vary by plan Learn more →

On a Teams plan?
Reviews resume once this user has a paid seat and their Git account is linked in Qodo.
Link Git account →

Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center?
These require an Enterprise plan - Contact us
Contact us →

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 20, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-20T22:48:15.068662Z e223dc7 PR opened
🔒 Security Review ✅ Completed 2026-10-20T22:48:46.036919Z e223dc7 PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@Maverick0351a
Maverick0351a merged commit 903a5c7 into main Oct 21, 2026
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant