bug: Home navbar is white on first visit but transparent after internal navigation

Offen
#101 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
3/5
Geschätzter Aufwand
Ein halber Tag
Anfängerfreundlichkeit
35/100
Issue-Typ
Bug
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Bereich
frontend

Rechercherichtung

The navbar is the Home page header in the Next.js frontend; start from the component that sets its top background and the scroll-dependent white/backdrop-blur state, and compare the initial render with the client-side navigation path. Reproduce by loading the Home route fresh, then navigating away and back. Done when the top of Home is transparent in both cases and scrolling past the hero restores the blurred background.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

area:frontend bug

What happened?

On https://procoderji.com/, the Home navbar has a solid white background on the first visit. After navigating to another page and returning Home, it becomes transparent and the yellow gradient/grid continues behind it.

The owner reported this in production and supplied two desktop screenshots showing the inconsistent states. The root cause has not been confirmed; this report does not claim an independently reproduced browser result.

Steps to reproduce

  1. Open the Home page in a fresh browser session, with the page at the top.
  2. Observe the white navbar bar above the yellow hero.
  3. Navigate to another page using the site navigation.
  4. Return Home and compare the navbar at the top: it is now transparent.

Expected behavior

At the top of Home, the navbar should be transparent on both initial visits and return navigation. The yellow hero background and grid should continue behind it without a white bar or hard edge.

After scrolling past the hero, the existing light white background and backdrop blur should keep navigation readable.

Environment

  • Production: https://procoderji.com/
  • Release commit: 9e2b9c00556de0387b09e937ffbefbd4eb9e0919
  • Desktop screenshots supplied by the owner; browser/version not recorded.
  • Mobile behavior should be checked when this is investigated.

Acceptance criteria

  • Fresh-session entry and hard refresh show the transparent navbar at the top of Home.
  • Returning Home through internal navigation produces the same appearance.
  • Scrolling beyond the hero still enables the white/blurred background.
  • Desktop and mobile navigation retain their current links, layout and brand styling.

Planning

Reported for the backlog. Investigation and implementation are deferred until scheduled; no fix or pull request is requested at this time.

Vorherrschende Sprache
TypeScript
Sterne
1
Forks
1
Ø Merge
8 Std. 58 Min.
Gemergte PRs (30 T.)
37

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus procoderji-com/procoderji

Alle Issues in procoderji-com/procoderji

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.