I've been experiencing an issue whereby the Trickle button doesn't always display on the first article of each page of courses I'm developing.
- Behaviour 1: Trickle button displays, and the article below is locked until you click the button.
- Behaviour 2: Trickle button doesn't display, but the article below is unlocked and you can just scroll down to it.
This only happens when the first article of a page requires no other interactions (e.g. text & image) - as if Trickle is seeing the first article is 'complete' (no further interactions) and automatically unlocking the next article and then not displaying a button. Both behaviours can be seen on the exact same page on alternate visits.
Okay, so it's not locking users out from accessing the content, but it currently feels very inconsistent and it's been flagged by a client.
Is there some way to FORCE the trickle button to display and not unlock the next article even if the first article has no interactions?
I'm using framework 4.3.0 & version 3.0.1 of Trickle.