Scripture Links in Notes According To Bible Panel From Which Note Was Launched

For many years, the LOGOS mobile and web platforms correctly resolved scripture links in notes according to the Bible panel from which the note was launched. This panel-contextual behavior allowed seamless, contextual study across translations.

Example of prior behavior:
- Opening a note from the KJV panel → Pop-up displayed the KJV text.
- Opening a note from the NLT panel → Pop-up displayed the NLT text.

Recently, this behavior appears to have changed:

Regardless of which Bible panel the note is launched from, the scripture pop-up now displays the “Top Bible”version instead.
This removes the ability to study notes within the context of the translation I am actively reading.
It also creates confusion when comparing translations side by side, because the pop-up no longer matches the originating panel.

Proposed Feature Restoration or Enhancement:

Please restore the ability for scripture links in notes to resolve according to the active Bible panel.

“Use Panel Context for Scripture Pop-Ups”

This would allow users to choose their preferred study experience without forcing a single global default.

Why This Matters:

It enhances study workflow for users running side-by-side parallel Bibles (which describes me).
It preserves expected contextual integrity during multi-translation comparison.
It aligns the Notes tool’s behavior with other LOGOS tools (e.g., linked panels, parallel resources).

Summary of the Problem:

Situation	Desired Pop-up Behavior	Current Pop-up Behavior
Open note from KJV panel	Pop-up in KJV	Pop-up in Top Bible
Open note from NLT panel	Pop-up in NLT	Pop-up in Top Bible

Find more posts tagged with

Submitted

Status: Submitted

Comments

Dave Hooton

I'm more accustomed to the Desktop, but I'll address your issue using the web app.

Regardless of the bible used the Note contents will depend on how/where it was created:

Note by reference: the Anchor Pop-up will always reference Top Bible
- as this note will display in any bible the Pop-up bible is surely irrelevant?
Note by selection: the Anchor Pop-up will reference Top bible and the bible that created the note
- e.g. Anchor: Genesis 33:10 KJV —> the passage links to Top Bible whilst "KJV" links to the KJV bible.
- Note that Web app does not display a note created in another bible, so the above will not display in NLT Bible.

Have I understood your issue?

Loyd Wolfley

Hi Dave Hooten.

Thank you for your interest and response. I am not certain that I understand your comment; therefore, I am unable to ascertain whether or not you understand my issue.

As a preliminary matter, I use the mobile app about 98% of the time, Desktop version about 2% of the time and the web browser version never. However, my issue exists in all three versions.

I am unable to better describe my issue, so let me demonstrate with screenshots taken from the mobile app (screenshots attached).

My layout is two vertical panels, with the King James Bible panel on the left and the NLT Bible panel on the right.
Current Situation:The King James Version is the Set Top Bible and has always been the Set Top Bible.Opening a Note from the KJV Bible panel, then clicking on the scriptural link within the Note, results in scripture being displayed in the KJV, accompanied by an icon and King James Version footnote under the scripture.Opening a Note from the NLT Bible panel, then clicking on the scriptural link within the Note, results in scripture being displayed in the KJV, accompanied by an icon and King James Version footnote under the scripture.

Perhaps the app is functioning as currently intended; however, the foregoing was not the status quo as far back as I can remember... until sometime in the last few weeks.

Former Situation: The King James Version has always been the Set Top Bible.
Opening a Note from the KJV Bible panel, then clicking on the scriptural link within the Note, resulted in scripture being displayed in the KJV, accompanied by an icon and King James Version footnote under the scripture.Opening a Note from the NLT Bible panel, then clicking on the scriptural link within the Note, resulted in scripture being displayed in the NLT accompanied by an icon and New Living Translation footnote under the scripture.

The recent change results in the scriptural link no longer being Bible panel context specific. Currently, the scriptural link always displays scripture according to the Set Top Bible only.

As it stands, there is no easy way to view the scriptural link in the NLT.

I trust this makes sense.

Thanks again.
Loyd Wolfley

I would need to see the Note at Jn 6:44 (in the Notes tool) But it appears that your mobile is iOS whereas mine is Android

When I tap the Note icon at Gen 33:10 in NLT (for example) it displays the content e.g.

Isaiah 54:3
	Edit note »

When I click the reference, the verse text is shown followed by Jump to reference »
The link takes me to Is 54:3 in the NLT.
My Top Bible is ESV.
The Wepp app opens the link in ESV.

So if this is correct, the problem lies with iOS mobile and Web App.

Loyd Wolfley

If I understand you correctly, you have verified the following platform behavior when tapping scripture references in Notes:

Platform	Note Reference Behavior	Pop-up Bible Used
Android	Honors originating panel	✅ Contextual Panel

I have verified the following platform behaviors when tapping scripture references in Notes:

Platform	Note Reference Behavior	Pop-up Bible Used
iOS (Mobile)	Ignores originating panel	❌ Top Bible only
Web App	Ignores originating panel	❌ Top Bible only
Desktop	Ignores originating panel	❌ Top Bible only

It appears that only the Android app currently honors the originating panel’s translation context when tapping a note link. All other platforms override this and display the “Top Bible” regardless of panel origin.

If the foregoing is correct, then the problem is not caused by:

My personal settings
My devices (MacBook, iPad)
The Chrome browser (in which the web version was displayed)
My local operating systems (macOS, iOS)

I contend that the problem is caused by platform-level inconsistencies in how Logos software handles Notes across its apps. Specifically, the Logos software itself (Web, iOS, macOS Desktop) fails to preserve panel context when resolving note references — except on Android.

The problem that I am describing represents a regression from previously correct behavior. The Android app proves this feature is technically feasible and already implemented properly on at least one platform.

In my opinion, the Faithlife / Logos Software Development Team should investigate the problem, as this appears to be a case for engineering-level review, because there is an inconsistency between platforms; thereby, violating cross-platform expectations.