From edbackell at gmail.com Wed Jan 17 13:32:17 2024 From: edbackell at gmail.com (Ed Backell) Date: Wed, 17 Jan 2024 10:32:17 -0800 Subject: [xiphos-users] Slightly odd behavior - reason? Message-ID: Hello, all. As I was studying this morning, I wanted to quickly page back and forth between chapters. I noticed that as I scrolled to the bottom of a chapter, I could click on the first verse of the NEXT chapter, and I'd advance to that chapter. So when I tried it with the PREVIOUS chapter, it didn't seem to work... UNTIL I noticed that if a verse has a link embedded in it (like the NET translation, for example), the only clickable parts that will advance you forward or back MUST BE before the link appears in the verse. In other words, the very first word in a verse in the previous or the next chapter will advance you... but any words in those verses that happen to be in a link will NOT. Is this a known behavior? Is it easy to alter? KFJ - Pastor Ed Warden Community Church -------------- next part -------------- An HTML attachment was scrubbed... URL: From karl at kleinpaste.org Wed Jan 17 15:00:04 2024 From: karl at kleinpaste.org (Karl Kleinpaste) Date: Wed, 17 Jan 2024 15:00:04 -0500 Subject: [xiphos-users] Slightly odd behavior - reason? In-Reply-To: References: Message-ID: <7e7c9948-a575-4c3e-9bb8-2a31def22cb5@kleinpaste.org> On 1/17/24 13:32, Ed Backell wrote: > Is this a known behavior? Is it easy to alter? Yes. No. The code wraps the entire verse text in to make it clickable. Then the problem becomes that internal linkages in the module markup also using create an HTML inconsistency of the form some stuff here module-internal link here other stuff at the end. The result is that "some stuff here" is clickable but "other stuff at the end" is not. And frankly it's just on the good graces of the HTML interpreter that any of the links work at all, because it's a real inconsistency due to the fact that does not nest -- it would be fair, if unfortunate, for the HTML handling to just say "hm, ...and then ? who are you kidding, forget it." This wasn't noticed until long after the feature, if you can call it that, was in live usage, and tweaking the code to become sensitive to the internal linkages within the text hasn't been seen as worth the trouble. --karl -------------- next part -------------- An HTML attachment was scrubbed... URL: From edbackell at gmail.com Wed Jan 17 15:19:28 2024 From: edbackell at gmail.com (Ed Backell) Date: Wed, 17 Jan 2024 12:19:28 -0800 Subject: [xiphos-users] Slightly odd behavior - reason? In-Reply-To: <7e7c9948-a575-4c3e-9bb8-2a31def22cb5@kleinpaste.org> References: <7e7c9948-a575-4c3e-9bb8-2a31def22cb5@kleinpaste.org> Message-ID: thank you sir. I had kind of guessed it was something like that, and now that I *know* about it, I can always be sure just to click on the left edge of the verse where that first word is, because it's almost always going to be clickable. Just a matter of training my brain and my hands. Thanks! KFJ - Pastor Ed Warden Community Church On Wed, Jan 17, 2024 at 12:10?PM Karl Kleinpaste wrote: > On 1/17/24 13:32, Ed Backell wrote: > > Is this a known behavior? Is it easy to alter? > > > Yes. No. > > The code wraps the entire verse text in to make it > clickable. Then the problem becomes that internal linkages in the module > markup also using create an HTML inconsistency of the form > some stuff here module-internal link here > other stuff at the end. The result is that "some stuff here" is > clickable but "other stuff at the end" is not. And frankly it's just on the > good graces of the HTML interpreter that any of the links work at all, > because it's a real inconsistency due to the fact that does not > nest -- it would be fair, if unfortunate, for the HTML handling to just say > "hm, ...and then ? who are you kidding, forget it." > > This wasn't noticed until long after the feature, if you can call it that, > was in live usage, and tweaking the code to become sensitive to the > internal linkages within the text hasn't been seen as worth the trouble. > > --karl > _______________________________________________ > xiphos-users mailing list > xiphos-users at crosswire.org > http://crosswire.org/mailman/listinfo/xiphos-users > -------------- next part -------------- An HTML attachment was scrubbed... URL: