Repository navigation
Conversation
1196855 to
0888133
Compare
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 08881334d1
ℹ️ 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".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
0888133 to
b0eea52
Compare
wesbillman
left a comment
There was a problem hiding this comment.
No blocking defects found in this change. Reviewed head 50ac4bb3174564d2737d1eb9493beb2b83b39c47 against base 82d165d5b6fd7dc1f3e9784675d27c04aacdbeae, independently of #844. This is a comment review, not an approval.
- Behavior: the change reuses the shell’s existing disclosure and state owners, matches the complete contribution key, and retains built-in controls during startup. Four targeted Chromium/WebKit cases against the compiled app passed: a primary plugin page reclaimed exactly 260px, preserved its draft and mounted sidebar, excluded hidden controls from keyboard/role navigation, and retained drawer/Escape/destination-focus behavior. Coverage included both themes, 100%/200% text, 650/651px resizing, a 390px drawer, reduced motion, and visits between primary pages. Production sources were unchanged during these probes.
- CI caveat: all 9,199 Vitest tests and all 12 browser journey shards passed, but JavaScript (1/2) failed on an unhandled Sonner timer (
window is not defined), attributed toWorkflowsPage.test.tsx. That test mountsWorkflowCommunitydirectly, notAppShell; its code and the toast dependency are unchanged here. This is outside this diff’s execution path, but required CI remains red and needs separate resolution/disposition. - Remaining acceptance: the PR’s human test is still pending. These browser probes do not certify native webview, VoiceOver, or physical-touch behavior. No additional code changes requested by this review.
Carl, an automated reviewer, commenting via Wes’s GitHub account.
Co-authored-by: Codex (gpt-6-luna) <noreply@openai.com> Signed-off-by: Kyle Zemek <kylez@squareup.com>
Co-authored-by: Codex (gpt-6-luna) <noreply@openai.com> Signed-off-by: Kyle Zemek <kylez@squareup.com>
Co-authored-by: Codex (gpt-6-luna) <noreply@openai.com> Signed-off-by: Kyle Zemek <kylez@squareup.com>
50ac4bb to
2b6eabf
Compare
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: Kyle Zemek <kylez@squareup.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: Kyle Zemek <kylez@squareup.com>
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 3b1ad3077f
ℹ️ 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".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
Status since the approval at
The human test from the contribution checklist is still pending, so — Posted by Claude Code (claude-opus-5-5) on behalf of kylez |
TL;DR
Primary plugin pages can now hide and restore the shell sidebar. Plugin pages that provide their own navigation can reclaim the left rail.
Why
The shell currently enables collapse only on Channels, Me, and Settings. Other primary pages cannot hide the shell navigation.
What
How
AppShell checks whether the selected page key matches a primary registration. The existing open state, narrow drawer, and accessibility handling remain in place.
Risk
This changes shell sidebar eligibility and its label only. It does not add a page navigation API.
Browser coverage
tests/browser/navigation.spec.mjs"a collapsible sidebar yields to narrow drawer styles during resize" (Chromium and WebKit). It needs a real browser because it asserts the computed cascade between the desktop collapsible-sidebar rule and the narrow-drawer media query, which jsdom does not compute.sidenav-polish.spec.mjsnow expects the generic "Show sidebar" label, and the sharedsettleShellTogglehelper accepts the generic and Me labels. No browser cases were removed, so no replacement coverage is needed.3b1ad30, with this PR's 3-line narrow-drawer rule inglobals.cssremoved, the new case fails in WebKit atnavigation.spec.mjs:26(displayexpectednone, receivedgrid). With the rule restored, it passes in both engines. Chromium passes either way.AppShell.test.tsxcovers a primary plugin page hiding and showing the sidebar, a non-primary plugin page staying non-collapsible, and built-in controls before page contributions load.Test plan
Human test pending. At a desktop width, open a primary plugin page and click "Hide sidebar"; the shell navigation should disappear, its controls should leave keyboard and accessibility navigation, and the left rail should be available to the page. Click "Show sidebar"; the shell navigation should return. At a narrow width, verify the existing "Show navigation" and "Hide navigation" drawer still opens and closes.
Related work
This change complements the page-owned sidebar contribution in #844.
— Posted by Codex (gpt-6-luna) and Claude Code (claude-opus-5-5) on behalf of kylez