Tech Forum

URLs that are supposed to take you to a specific verse in the scriptures have been broken for several weeks. I normally use Chrome, but decided to check Firefox and Microsoft Edge and found that that automatic scrolling/jumping to a specific verse when "#[verse_number]" is in the URL was also broken in Firefox. However, it did work in Microsoft Edge although was not consistent in the placement (more on this below). I'm running the latest versions of all 3 browsers on Windows 10 Fall Developers edition.

For Example:
The following URL will not automatically scroll/jump you down to verse 56 in D&C 45 in Chrome and Firefox, but it will put you in the middle of the verse in Microsoft Edge (highlighting of verse 57 still works in all browsers):
https://www.lds.org/scriptures/dc-testa ... ang=eng#56

Note that with the previous link in Microsoft Edge, it does not scroll/jump the beginning of verse 56 to the top of the page, but scrolls/jumps slightly past the beginning of verse 56. I tried a couple of other similar URLs and some exhibit the same behavior of going past the beginning of the verse, while others scroll/jump to the beginning of the verse noted by "#[verse_number]" rather than part-way through the verse. (Again scrolling/jumping to the verse only occurs with Microsoft Edge currently)

I'm also posting this to the "Feedback Page" on lds.org (https://www.lds.org/tools/feedback/?lan ... ment:dc:45) since I'm not sure where the best place to report issues is.

Thanks for posting this. I've noticed the problem, too. I'm glad you reported it through Feedback. It seems to periodically be broken and later fixed.

I've just noticed this now, too.

The HTML IDs for the verses have changed – if you add "p" (as in "paragraph") to the number it should work:
https://www.lds.org/scriptures/dc-testa ... ng=eng#p56

The problem is that the church needs to update its content with the new format.

Sorry for the delay in thanking you for your answer and ideas. They are much appreciated. Does anyone have any idea if this issue is something that can be turned into a tech.lds.org project and farmed out to the community to fix or is it too interwoven into the codebase to have this done by external resources? If it's the latter, how can this issue be given more notice to the internal LDS tech team such that its priority can be bumped up?

At this point, I would recommend adapting to the new scripture pages under https://www.lds.org/languages/eng/lib, and reporting bugs there (the older scripture pages are unlikely to receive updates). For example, this verse took me to verse 57 and highlighted it:
https://www.lds.org/languages/eng/conte ... /45.57#p57