Bible Address Box Not Working

ASUNDER · 2025-02-05T23:42:32+00:00

There was an error rendering this rich post.

I've noticed this several times. When wanting to jump to somewhere else, I type in the place I want to go and it completely disregards what I just typed in. This time I keep typing in 'Peter 1' and then the box just reverts back to Zech 14, as if I didn't type anything.

If I can't use the address box to navigate to different books, I'm dead in the water. How do you even go anywhere without a steering wheel?
It's like it gets stuck and can't move until I close and reopen a new Bible tab. Then it works again.

Find more posts tagged with

Comments

MJ. Smith

The navigation box works the same way as the generic command line - it expects you to select otherwise it takes the top option. See

https://community.logos.com/discussion/246142/active-box-changes-search

Both of these are cases where you will learn the cadence of the program and have few problems … but until you learn that cadence it can be very frustrating.

NB.Mick

I've noticed this several times. When wanting to jump to somewhere else, I type in the place I want to go and it completely disregards what I just typed in. This time I keep typing in 'Peter 1' and then the box just reverts back to Zech 14, as if I didn't type anything.

"Peter 1" is not a valid location in your bible, is it?

Bradley Grainger (Logos)

This time I keep typing in 'Peter 1' and then the box just reverts back to Zech 14, as if I didn't type anything.

"Peter 1" is not recognised as a valid reference, so that input is ignored. Anything that can be understood as an unambiguous reference will be used for navigation, though. You could enter "1p1" or even "1p" to navigate to 1 Peter.

ASUNDER

Oh I see. I was typing it backwards. I was going for 1 Peter.
To be honest if the AI search can figure it out I think the address box should too.

I think what would be ideal is if we type something wrong, but partially matches (fuzzy) with something, it should enter in the correction into the box but not execute the search. We will have to push Enter again to search it.

So if I type 1 Pet it should behave as normal, going to 1 Peter and displaying the exact "1 Peter" in the box.
But if I type Pet 1 or something like that the text should snap to 1 Peter, keeping it highlighted and focused but it won't search, just in case what I want and what it snapped to isn't the same thing. And also reminding us of what we did wrong. Either way a void of any response is no good. It makes the person think it's bugged out; not knowing the reason for this is a wrong query.