2026-02-25T01-25-55_auto_memory/memories.db-wal, memory/memories.db-wal, me
This commit is contained in:
parent
b631965d8e
commit
2d796c00f6
@ -0,0 +1,11 @@
|
||||
# 2026-02-25 Session Notes
|
||||
|
||||
## Oddcore Website Loader Animation Bug Fix
|
||||
|
||||
Nicholai reported a persistent issue with the page loading animation on the oddcore-website project. The animation was appearing for a split second between navigations, and after attempted fixes, it became stuck on screen completely, refusing to disappear. He requested a proper implementation.
|
||||
|
||||
The Loader component (src/components/Loader.tsx) uses React hooks with GSAP for animation sequencing. It initializes visibility state synchronously from sessionStorage (checking 'oddcorp-loader-seen') to avoid showing the overlay on repeat visits. The animation timeline runs for ~2.8 seconds total: progress bar fills over 1.5s, logo fades and blurs over 0.5s (with 0.2s overlap), then the container slides up over 0.8s.
|
||||
|
||||
On animation completion, the onComplete callback should call setIsVisible(false) and set the sessionStorage flag. The component has a click handler to skip the animation. The useEffect dependency array is empty, suggesting the animation should only initialize once.
|
||||
|
||||
The issue appears to be related to animation lifecycle management or state synchronization—either the onComplete callback isn't firing properly, or the setIsVisible(false) isn't being applied correctly. Session investigation started by examining the current Loader implementation to identify the root cause before implementing a fix.
|
||||
Binary file not shown.
Binary file not shown.
Binary file not shown.
Loading…
x
Reference in New Issue
Block a user