nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

BUG: 4.6B2 Multi Columns appear and disappear when navigating certain resources

Richard Lyall

I'm paging up and down through ESV Study Bible at the beginning of Isaiah and I notice something odd. I have it set to display in 2 columns.

This works are expected until I reach logosres:esvsb;ref=Page.p_1232;off=744 where the Activity of the Writing Prophets ... table appears. The display now only shows 1 column, though the Resource Menu still shows "2 Column" view selected. I scroll back through Isaiah until I reach logosres:esvsb;ref=Page.p_1236;off=3274 at which point the 2 columns reappear, and the Resource menu continues to show "2 Columns" all the while.

This behaviour is 100% reproducible, and occurs at two different zoom levels.

This is probably something to do with the fact that the table mentioned above is greater than the width of a single column. But why the two column view is only restored when the map on p1236 appears ... is this a bug?

Thanks
Richard

Find more posts tagged with

Comments

Richard Lyall

Yeah definitely something weird here. Once the displayed column count comes to mismatch the column count in the menu, then changing the column count via the menu has no effect on the displayed column count.

Tonya J Ross

https://community.logos.com/discussion/comment/385380#Comment_385380

This behavior is by design. As you have noted with the table being too large to display in less than one column, the program will switch to less columns to avoid breaking a table, image, or heading across multiple lines. The display will revert back to the desired setting after it reaches the next article break (so it may take a few pages in either direction.)

Richard Lyall

https://community.logos.com/discussion/comment/385537#Comment_385537

Makes sense. It might make more sense though to revert to the selected column count once the oversized article is out of view, rather than waiting for the next article break?

Tonya J Ross

https://community.logos.com/discussion/comment/385540#Comment_385540

According to dev:
"It has to do with how we
measure/wrap our article content. We wrap all loaded content to
the same width (i.e. same number of columns). So, when some content is loaded
that doesn't fit, all content is measured/wrapped to fit at the lowest common
denominator. We don’t remeasure/wrap until we load or unload more content. Once the offending content is unloaded the display will return to the set number of columns (unless of course new offending content was loaded)."