Bug: Prioritize Books constantly scrolls back up to the top

Sean T · 2025-03-04T17:22:32+00:00

There was an error rendering this rich post.

This may be Mac-specific as I don't recall noticing this on Windows, but I'm trying to manage my prioritize feed with two separate library windows, and I'm dealing with constant issues of it auto-scrolling back up to the top of the list.

I've had it occur just when dragging resources from the prioritized list on the left to the prioritized list on the right, but it consistently occurs if I just have another tab open next to one of the Library tabs, switch to that tab, and then back to the Library tab.

Find more posts tagged with

Bug

Mac

Prioritization

Library

Desktop App

Comments

Dave Hooton

NB. This was moved from the English Feedback forum to the English Forum, with another Tag added.

Why are you dragging between two Library panels when you can drag in one panel?

If both tabs are visible as below and I've set the destination (bottom) List to the position required, it will scroll when dragging a book from the source (top) List in Windows.

The top panel is adjacent to other tabs whilst the bottom panel is by itself.

I doubt that this will get any traction with Faithlife as Prioritization was intended to be performed in one Library tab.

Sean T

Screen Recording 2025-03-05 at 10.09.57 AM-Animated Image (Large).gif

There were two scenarios where I mentioned this was a problem. One of the scenarios would still land squarely in your claim that Prioritization is only intended within one Library tab, and I've attached a GIF demonstrating that. I can't scroll down, temporarily switch to another tab, and switch back without losing my place.

To directly address your objection, it's a mistake to address user feedback by saying "that's not how they intended it" without working to understand the user needs. I assume you've been using Logos for a long time and have just accepted it as it is. I'm coming at it with fresh eyes, and prioritization has major problems (I've reported a number of issues in feedback already).

Here's the scenario explaining why I was doing it: I have an extensive prioritization configuration, but I wanted to rework some of it. I opened two Library tabs side-by-side (not above and below each other). This allowed me to scroll down into the area of prioritization I wanted to work in and stay in that context while I search the prioritization list in the other tab, find the one I need, and drag it into the new location (via the context I've established in the other tab).

I'm pretty sure I picked up this technique while watching one of Jason Stone's interviews with users.

Regardless, I'm less concerned with what they intend and more concerned with how it should be.

As a software developer, I understand the complexities of feature implementation, so I get that this might be complicated to fix. As a software engineering leader, I also have a good perspective of feature prioritization, how past decisions / technical debt can make changes more difficult, and the tradeoffs that teams make as they work together with product management to ship things out the door.

I don't have any historical knowledge of the introduction of the prioritization feature. However, it seems that Logos is increasingly adding / improving features that directly rely on that feature (Factbook, Insights Panel, click navigation in general). Despite that, it appears to have had no attention to it whatsoever. It's a critical aspect of how the software provides information the user needs based on the features they use. My hope is that Logos sees the importance of it and is driving behind the scenes to make some improvements here. My fear is that they view it as a one-time cost (set it and forget it), and they don't realize it's more important than that. It has onboarding and user engagement impact but looks like it was added as an afterthought.

Dave Hooton

@Sean T. To directly address your objection, it's a mistake to address user feedback by saying "that's not how they intended it" without working to understand the user needs. I assume you've been using Logos for a long time and have just accepted it as it is. I'm coming at it with fresh eyes, and prioritization has major problems (I've reported a number of issues in feedback already).

Fair enough. It can be tougher coming from the Developers, though. But I did confirm that your method also causes scrolling in Windows 11.

I could not confirm scrolling within a single Library tab, though.