Skip to content

QA: Map page fixes and empty state text#320

Open
bryceerobertson wants to merge 1 commit intomainfrom
bryce-QA-map
Open

QA: Map page fixes and empty state text#320
bryceerobertson wants to merge 1 commit intomainfrom
bryce-QA-map

Conversation

@bryceerobertson
Copy link
Copy Markdown
Member

  • Add invisible hover bridge between map logo circles and label pills to prevent tooltip flicker (matching live site behavior)
  • Use 'Long name' Airtable field for map tooltip instead of 'Long name for cards' so bracketed acronyms (e.g. "CARMA") don't appear
  • Make items with no link (e.g. "Last updated") non-clickable on the map while still displaying them
  • Replace browser native smooth scroll with custom 500ms quadratic ease-out animation for the "View cards" button
  • Change empty search state text from "No items found." to "Nothing found." across all resource pages

🤖 Generated with Claude Code

- Add invisible hover bridge between map logo circles and label pills to prevent tooltip flicker (matching live site)
- Use 'Long name' field for map tooltip instead of 'Long name for cards' so bracketed acronyms don't show
- Make items with no link (e.g. "Last updated") non-clickable on the map
- Replace browser smooth scroll with custom 500ms quadratic ease-out for "View cards" button
- Change empty search state text from "No items found." to "Nothing found." across all resource pages

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@vercel
Copy link
Copy Markdown

vercel bot commented Mar 24, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
ai-safety-com Ready Ready Preview, Comment Mar 24, 2026 5:00am

Copy link
Copy Markdown
Collaborator

@jakkdl jakkdl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Small nitpick: I'd reword some of the comments to be about why the code is there, rather than why it was added - but not worth fiddling with.

I'm a bit torn on the custom scroll animation, that seems like the type of technical debt / semi-magical math one should be vary of cause it could easily break/not handle edge cases/etc. I also suspect the scrolling would feel better if we try to improve the performance of the page.
We likely also want the same behavior on the communities map? in which case it should be pulled out into a shared utility.

And Claude thinks there ideally should be an accessibility handler if a user has set prefers-reduced-motion (this was previously handled by the built-in scrollTo)

But it does feel slightly smoother, so I'm not opposed to adding it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants