Improve UnsupportedBrowser with browser-specific guidance and download links

[kanweiwei]

When users visit CreatorWeave with an unsupported browser, they see UnsupportedBrowser.tsx. Currently it's minimal — we'd like to make it more helpful.

What to do:

1. Read web/src/components/UnsupportedBrowser.tsx
2. Enhance it to:
   • Detect the user's current browser and version
   • Show browser-specific guidance (e.g., "Your Firefox needs COOP/COEP headers configured")
   • Provide download links for Chrome/Edge
   • Show a compatibility table (Chrome 86+, Edge 86+, etc.)
   • Add i18n support for the new strings
3. Ensure the component works without File System Access API

Skills needed: React, TypeScript, basic browser API knowledge

Estimated time: 2-3 hours

[snakefood3232]

I'll enhance UnsupportedBrowser.tsx with browser detection and specific guidance as requested. I'd implement a robust browser detection utility and add i18n-ready strings with compatibility tables and download links. Can have this PR ready in 2-3 hours—I've built similar browser compatibility components for production Next.js apps.

[snakefood3232]

I'll enhance UnsupportedBrowser.tsx by detecting the user's browser/version and adding specific guidance with download links. I'd implement a lightweight browser detection library and integrate i18n for the new strings while avoiding File System Access API dependencies. I can have a PR ready in 2-3 hours—I've built similar browser compatibility components for production Next.js apps.

[snakefood3232]

I'll enhance UnsupportedBrowser with browser detection and specific guidance per the issue. I'd handle this by using user-agent parsing for detection, adding i18n keys for new strings, and implementing a clean compatibility table. Can have a PR up in 2-3 hours—I've built similar browser compatibility components for production Next.js apps.