test: update favourites auth gate assertion - #1357
Conversation
…ructure-b2bf # Conflicts: # src/components/clinical-dashboard/ClinicalSidebar.tsx
Land the six-item sidebar (Answer, Documents, Services, Medications, Factsheets, Tools) plus settings-guide flow and lazy sidebar dialogs on current main. Keep main's clinical-dashboard-lazy barrel and phone shell classes; replace main's Forms/Therapy rail composition with #66's set. Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com>
Assert the canonical sidebarToolItems list (Medications/Factsheets) instead of main's retired primarySidebarToolIds Forms/Therapy filter. Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com>
Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com>
…em-land-cfa0 Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com>
Tighten mobile menu assertions so Close Clinical Guide menu is not treated as a Guide affordance, and make openGuide reuse an already-open Settings dialog (tablet rail + restore path) instead of clicking through an overlay. Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com>
…0' into cursor/sidebar-six-item-land-cfa0 Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com>
Record feature-branch proof on PR #1174 (focused suites, verify:pr-local, ensure spot-check, verify:ui). Remaining work is merge to main. Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com>
Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com>
Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com>
Cite d97c11e as the content-proof commit for the six-item sidebar land so later ledger-only tip moves do not churn the issue row. Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com>
Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com>
…em-land-cfa0 Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com>
This pull request has been ignored for the connected project Preview Branches by Supabase. |
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in:32 minutes Your organization has reached its usage spending cap. Adjust your spending cap in the billing tab. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (12)
Comment |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit:0c2e8e5a09
ℹ️ 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".
| closeLabel="Close settings" | ||
| labelledBy="account-settings-title" | ||
| initialFocusRef={closeButtonRef} | ||
| initialFocusRef={initialFocus === "guide" ? guideButtonRef : closeButtonRef} |
There was a problem hiding this comment.
Scroll the restored Guide control into view
When Guide is opened from Settings and then closed, SidebarSettingsDialog has unmounted the settings surface, so it remounts with its scroll container at the Account section; this ref targets the Guide button near the bottom, but Sheet focuses it with preventScroll: true. The result is keyboard focus on an off-screen control with no visible focus indicator on both phone and shorter desktop viewports. Preserve/restore the prior scroll position or scroll the Help section into view before focusing; a focused browser check should assert that the Guide button's bounds are inside the settings scrollport after closing Guide.
Useful? React with 👍 / 👎.
Summary
RAG impact