Fix GIPHY UI cache mismatch
build-push / docker (push) Successful in 4m18s

This commit is contained in:
GHStaK
2026-03-24 16:50:20 +09:00
parent e79d15de2e
commit f5ceb872e0
3 changed files with 24 additions and 20 deletions
+13
View File
@@ -268,6 +268,19 @@
- backend debug broadcasts
## Recent Change Log
- Date: `2026-03-24`
- What changed:
- Removed the large GIPHY image-mode info box entirely and replaced it with a minimal inline prompt bar plus `Powered by GIPHY` label.
- Hardened frontend visibility toggling so stale cached HTML/JS combinations do not crash on missing elements.
- Bumped the frontend asset version again so browsers are forced onto the latest image-search UI bundle after the GIPHY panel changes.
- Why it changed:
- Real user logs showed a client-side `Cannot read properties of null (reading 'classList')` error caused by stale frontend asset mismatch, which prevented image results from rendering, and the remaining large image-mode box was still not desired in the UI.
- How it was verified:
- log review of `ai-media-hub-2026-03-24T07-48-19-085Z.log`
- `node --check frontend/app.js`
- What is still risky or incomplete:
- Users with aggressively cached browser sessions may still need one hard refresh to fully drop older HTML/JS combinations already loaded in an open tab.
- Date: `2026-03-24`
- What changed:
- Simplified the GIPHY image-search UX so it presents raw search results instead of looking like an AI-evaluated result flow.