Repository navigation
fix(docs): polish code rendering and keyboard navigation - #9827
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
[Medium impact] The PR appears safe to merge; no blocking issues were found. SummaryThe PR polishes docs code rendering and keyboard navigation.
The latest changes preserve one keyboard entry per API sample. No actionable new issues or rule violations were found. No previous review threads were supplied. Builds, tests, and browser checks were not run during this review. Reviews (2) · Last reviewed commit: "fix(docs): give API samples one keyboard..." · Reviewed by Greptile |
There was a problem hiding this comment.
All reported issues were addressed across 8 files
Reply with feedback, questions, or to request a fix.
Turn on auto-fix | Re-trigger cubic
|
@cubic-dev-ai review this PR |
@waleedlatif1 I have started the AI code review. It will take a few minutes to complete. |
…iring Carries #9827's keyboard-reachable code samples and tabs into the docs components this branch moved to emcn-docs, and records CodeContent's tabIndex in the EMCN surface snapshot.
Summary
Type of Change
Testing
Checklist
test-auditauthoring gate)