Obervation regards autoscroll to a tiddler opened in the storyriver

Just an interesting observation.

For ergonomic reasons I have created clickable screen profiles that allow me to use a large screen at a distance. The outcome is I can move from my desk and instead work from a sofa at a distance with a wire free keyboard and mouse. The screen profile for the large screen uses much larger font which I can read easily from a distance, fewer characters on each line of tiddler content and so tiddlers are proportionately considerably greater in height and so much longer scroll distances involved.

I noticed that the autoscroll to a freshly clicked tiddler link no longer seemed to work, yes there was some autoscroll but the tiddler in question did not appear.

Then on a hunch I tried clicking on the link in the sidebar repeatedly and then after 4 clicks or so the tiddly finally appeared after several incremental scrolls.

It seems that the autoscroll was working but was effectively limited so that it could not get to the desired tiddler in one long step but would get there eventually in mini-steps.

As far as I am aware the behaviour is seen when the target tiddler is already on the storyriver but distant in terms of the required scroll from the current view of the storyriver. I can reproduce the behaviour by having a lot of open tiddlers and using the “Open” tab on the sidebar and simply choosing a target tiddler on the Story river a long way from my current scroll position.

Its not a problem for me now I know the workaround but this issue might affect people with accessibility difficulties so I thought worth flagging.

The larger font in my case is achieved partially by a modest increase in default font sizes in my chosen theme (usual method in TW settings) but that setting applies for all screens that I use (mobile, desktop and now the 40" screen I use whilst on the sofa) but the big changes invoked for the 40" screen are managed by a separate CSS screen profile which I can invoke on a custom sidebar tab - the 40" profile typically using around 3rem as a “multiplier” I am still fine tuning this.