feat(ui): add loading spinner to version switcher#156
Conversation
Add a subtle loading spinner to the version switcher dropdown in the Javadoc while it fetches available versions from the GitHub API. This micro-UX improvement uses a CSS background image tied to the aria-busy state to provide immediate visual feedback during asynchronous operations, improving the perceived performance and usability of the documentation site without requiring any new dependencies. Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com>
|
👋 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 New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
|
1 participant
What: Added a subtle loading spinner (an animated SVG icon) to the documentation version switcher dropdown while it fetches versions.
Why: The version switcher makes an asynchronous call to the GitHub API to get available tags. Before this change, the dropdown just said "Loading versions..." which could be missed or feel unresponsive if the network request was slow. The spinner provides clear, immediate visual feedback that an operation is in progress.
Before/After: Before, the dropdown displayed text only. After, the dropdown displays an animated rotating circle alongside the loading text.
Accessibility: The spinner leverages the existing
aria-busy="true"attribute already set via JavaScript, ensuring that screen readers also convey the busy state to assistive technology users.PR created automatically by Jules for task 18010929459732205417 started by @Tugamer89