Just lost about an hour again because of this. Didn’t recognise it from the start:
I have a Panel which is displayed based on a display JS Observable.
The Observable is set asynchronously, if a flag file doesn’t exist. The check was done in an Activated handler. It would just set display.value = true, if the flag is not there.
Yet, only on restarts the Panel would show. Even if the Activated trigger executes on each page load. Why? Because the display Observable gets detached and sequential value changes don’t trigger the WhileTrue I was using to toggle visibility.
This is a serious limitation for Activated - you can only use it for non reactive stuff or only for one time value setting…
Costin: Okay, sorry to hear that. Do you have an isolated test case that shows this issue? If so, I can do some debugging on this.
Yo Anders! The test case at the top still holds, even if it refers to navigation. It seems it’s more an Observable and Activated issue, than anything else.
Thanks. I’ve reproduced the problem. This is indeed strange, so raising this to top priority.
I’ll keep you posted.
Whops, this is an embarrasing one.
Indeed, the onActivated function on the previous module was called due to a missing cache invalidation in the event binding system.
This is now fixed!
Due to the embarrasingness of this bug, we’ll attempt to get it cherry-picked onto release 0.29, about to go out very soon (today, you can find it in #pre-release-testing on slack).
Thanks so much for reporting this issue and patiently pushing it forward.