feat(benchmarks): animate progress bars and add scroll-triggered counter - #470
Merged
ilteoood merged 4 commits intoJul 26, 2026
Merged
Conversation
- replace native <progress> with a div-based track/fill for reliable cross-browser color rendering - animate req/sec count-up and bar fill together, driven by a single eased timer so they stay perfectly in sync - trigger the animation on scroll into view via IntersectionObserver - respect prefers-reduced-motion - restyle cards: custom resting/hover shadow (drop shadow--md), subtle border highlight for the Fastify card, rank badge - match bar color to the heading color (var(--ifm-color-primary))
Member
Author
|
@ilteoood one last improvement 😄 |
ilteoood
approved these changes
Jul 26, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Proposal:
Refreshes the
BenchmarkInfocard used on the/benchmarkspage:divelements instead of native<progress>, so the color renders consistently across browsers (native<progress>was falling back to the browser's default green in some cases)shadow--mdwith a custom resting/hover shadow)prefers-reduced-motionScreenshots:
before:
after:
ligtht-mode:
cc @fastify/website