Skip to content

🎨 Palette: [UX improvement] Add active state and aria-current to navigation#313

Draft
EffortlessSteven wants to merge 2 commits intomainfrom
palette/ui-navigation-active-state-7667996071145187860
Draft

🎨 Palette: [UX improvement] Add active state and aria-current to navigation#313
EffortlessSteven wants to merge 2 commits intomainfrom
palette/ui-navigation-active-state-7667996071145187860

Conversation

@EffortlessSteven
Copy link
Member

💡 What: Added a visual active state (bold, underline, purple color) and the aria-current="page" attribute to the main navigation links in the app-http UI.

🎯 Why: To improve usability and accessibility by clearly indicating to users which page they are currently viewing, mirroring the existing behavior in the http-platform UI.

📸 Before/After: Visual change in the navigation bar. Active links are now visibly styled differently.

♿ Accessibility: Added aria-current="page" to the active link to ensure screen readers correctly announce the current page context, adhering to WAI-ARIA best practices for navigation.

Scope

Type: UX/Accessibility Improvement
Intent: Enhance navigation usability and screen reader support by indicating the active page
Touchpoints: crates/app-http/src/platform/ui.rs
Evidence: Local UI testing (Playwright) confirmed visual state and DOM attributes. cargo test and cargo fmt passed successfully.


PR created automatically by Jules for task 7667996071145187860 started by @EffortlessSteven

Added `nav_link` helper closure to dynamically set `aria-current="page"`
on the active navigation item based on the current page context. Added
CSS styling (`font-weight`, `text-decoration`, `color`) to visually
distinguish the active link.
@google-labs-jules
Copy link

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

@coderabbitai
Copy link

coderabbitai bot commented Mar 25, 2026

Warning

Rate limit exceeded

@EffortlessSteven has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 4 minutes and 45 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: e76081a9-76a8-46ce-9ef7-9817a5fdebf5

📥 Commits

Reviewing files that changed from the base of the PR and between 90fd4d1 and 84505b9.

⛔ Files ignored due to path filters (1)
  • Cargo.lock is excluded by !**/*.lock
📒 Files selected for processing (1)
  • crates/app-http/src/platform/ui.rs
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch palette/ui-navigation-active-state-7667996071145187860

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@gemini-code-assist
Copy link

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly enhances the user experience and accessibility of the app-http UI by providing clear visual and programmatic indicators for the active page in the main navigation. The changes ensure that users can easily identify their current location within the application, while screen readers can accurately convey this context, aligning the app-http UI's navigation behavior with that of the http-platform UI.

Highlights

  • UX Improvement: Implemented a visual active state for main navigation links, making the currently viewed page clearly distinguishable with bold text, an underline, and a purple color.
  • Accessibility Enhancement: Added the aria-current="page" attribute to active navigation links, improving screen reader support and adhering to WAI-ARIA best practices.
  • Code Refactoring: Introduced a nav_link helper function to centralize the logic for rendering navigation links, including the conditional application of the aria-current attribute.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request refactors the UI navigation by introducing a nav_link helper function to dynamically generate navigation links and set the aria-current="page" attribute for the active page. Corresponding CSS styling has been added to highlight the active navigation item. The review suggests an improvement to the CSS by grouping selectors to avoid duplication of the text-decoration: underline property, enhancing maintainability.

Comment on lines +85 to +89
nav a[aria-current="page"] {
font-weight: 700;
text-decoration: underline;
color: #4c51bf;
}

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

There's a small duplication of text-decoration: underline; which is also present in the nav a:hover rule. To improve maintainability and avoid them getting out of sync in the future, you could group the selectors for this shared property.

For example:

nav a:hover,
nav a[aria-current="page"] {
    text-decoration: underline;
}

nav a[aria-current="page"] {
    font-weight: 700;
    color: #4c51bf;
}

This would involve modifying the nav a:hover rule (which is outside this specific change), but it would make the styling more robust and easier to maintain.

…erabilities

Upgraded astral-tokio-tar to v0.5.6 -> v0.6.0+ to resolve RUSTSEC-2026-0066
Upgraded rustls-webpki to v0.103.9 -> v0.103.10+ to resolve RUSTSEC-2026-0049
@github-actions
Copy link

Test Results

283 tests   245 ✅  10m 48s ⏱️
 25 suites   38 💤
  1 files      0 ❌

Results for commit 84505b9.

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