Fix bug with opening sources links - #3565
Conversation
📊 Code Quality Score: 1/100
Was this score accurate? 👍 Yes · 👎 No Scored by GitVelocity · How are scores calculated? |
There was a problem hiding this comment.
Pull request overview
This PR fixes navigation for “sources” search result cards when clicks are handled by in-app navigation (e.g., ReaderApp.handleNavigationClick / openPanel), by ensuring the click handler receives a proper text ref string instead of a URL path with query params.
Changes:
- Pass the underlying text ref (
tref) through the sources-mode search result card props. - Update
SearchResultCardto prefertrefoverhrefwhen invokingonResultClick, while keepinghrefas the actual anchor URL for normal navigation.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
static/js/SearchResultList.jsx |
Adds tref: s.ref to the sources-mode card props so the card can navigate using a real ref string. |
static/js/SearchResultCard.jsx |
Accepts tref and uses it for onResultClick(tref ?? href, ...); updates propTypes accordingly. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
stevekaplan123
left a comment
There was a problem hiding this comment.
I'm wondering why we need both tref and href. Is it possible we only need the tref?
We need href if we want to pass (for sources) url params to enable the text clicked to be highlighted when the text panel opens, see Claude's explanation below: |
Description
This PR fixes a bug where returned sources card title links wouldn't resolve.
Code Changes
Passing the ref through to the search result card