Minor but strange bug in the command box
If you type Insights on Revelation into the command box, you're only offered the choice of "Open Insights on Revelation to Revelation 2:1-7", rather than just "Open Insights on Revelation" as you would be with any other commentary.
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
Comments
-
Bump.
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0 -
Mark Barnes said:
If you type Insights on Revelation into the command box, you're only offered the choice of "Open Insights on Revelation to Revelation 2:1-7",
This is a very interesting bug...I wonder why it's only offering you that choice. I can reproduce it on both Mac and Windows and I will create a case for Development to investigate.
0 -
This was such an interesting issue I had to post about it.
We allow users to type "open ESV to Matthew" to open to a specific location. This makes sense and makes things that much faster. What may surprise you (at least it surprised me) is that we also allow you to type "open ESV on Matthew" to open to that location. Using the same logic when you type "open Insights on Revelation" it is parsed as:
[open] [Resource (Insights)] [to (on)] [Reference (Revelation)]
which turns into:
"open Insights on Revelation to [Best location in Revelation]We had* a similar issue with certain resources which begin with the word "Open" (Open Door on John).
*Expect this behavior to be corrected in the next beta
0 -
I'm glad to have been able to provide such interesting bugs for you (and glad that you've fixed it, of course!) [:)].
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0 -
This should be fixed in 5.2b beta 4.
0
