I also want to the navigate to the selected tiddler when it is selected from the select widget. For this I added the navigator widget, but its not working.
Thank you. It was just what I wanted too. It works perfectly in my wiki.
Are you using a theme? I ask because I have had small annoyances with some of them - especially the older ones
The “scroll into view” handling in the TWCore relies upon being able to scroll the entire page, which only works if the StoryRiver itself is NOT in a separate scrollable HTML div element, which is the case for the default layout, but might not be the case with your custom layout.
I ran into this issue when I implemented TiddlyTools/Stylesheet/TopBar, which allows you to pin/unpin and scale the TopBar. To make this work properly, it required that the StoryRiver div element can scroll independently of the whole page so that the TopBar doesn’t cover part of the StoryRiver, and optionally also allows the StoryRiver scrollbar to appear on the left side of the page. You can see this effect when you visit https://TiddlyTools.com. Note the pins in the top-left and top-right corners of the page, and the StoryRiver scrollbar on the left.
If your scrolling problem is caused by a similar issue, importing these two tiddler might fix it:
\whitespace trim
<!-- FORCES MOST-RECENTLY VIEWED HISTORY TIDDLER TO SCROLL INTO VIEW -->
<$list filter="[{$:/HistoryList!!current-tiddler}match<currentTiddler>]"><$scrollhere/></$list>
and TiddlyTools/Widgets/scrollhere.js defines the custom <$scrollhere/> widget, which uses browser-native Javascript functions parent.scrollIntoViewIfNeeded() or parent.scrollIntoView() to achieve the desired result.
After importing the above two tiddlers, save-and-reload so the scrollhere.js widget can take effect. Then you can test your scrolling problem and see if it has gone away.
The navigation issue occurs sporadically. So I have to investigate to find the reason. I will try your solutions today evening when I am back on the desktop.