fix(nav): unify mobile navbar surface - #80
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
devrodri-com
marked this pull request as ready for review
August 7, 2026 01:10
|
Bugbot is not enabled for your account, so this pull request was not reviewed. Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs. |
9 tasks
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
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.
What changed
bg-black/70,backdrop-blur-xl, andbackdrop-saturate-150surface on the shared navbar containerWhy
The top mobile bar and expanded panel used different backgrounds and backdrop filters. On iPhone this made the expanded navbar look like two separate surfaces. The outer navbar already wraps both regions, so the child panel only needed to stop painting a second surface.
Production and source discovery also confirmed that Servicios/Services was already present exactly once in the shared primary navigation registry. No navigation or copy change was required.
Validation
22.23.2; npm9.9.4npm cinpm run typechecknpm run lintnpm run test:run— 31 suites, 330 testsnpm run build— prerender and HTTP verification passednpm run ciReview gate