fix(footer): align legal link hover color with adjacent nav#8202
Merged
alexander-akait merged 2 commits intowebpack:mainfrom Apr 22, 2026
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Member
|
Please use only tailwind utils, no new classes |
Contributor
Author
@alexander-akait Addressed: removed the custom css and updated this to use tailwind utilities only. |
Member
|
/cc @evenstensberg can you look at this? |
evenstensberg
approved these changes
Apr 22, 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
3 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.
Summary
This PR fixes the hover state for the footer legal links so they match the hover color used by the adjacent page navigation links, while keeping the existing default blue link color unchanged.
What kind of change does this PR introduce?
fix
Did you add tests for your changes?
No new tests were added.
Does this PR introduce a breaking change?
No.
If relevant, what needs to be documented once your changes are merged or what have you already documented?
No additional documentation is needed.
Use of AI
no.
before
Screen.Recording.2026-04-20.at.3.27.21.AM.mov
after
Screen.Recording.2026-04-20.at.3.27.41.AM.mov