On Friday, July 10, 2020 at 1:16:16 AM UTC-7, Felicia Crow wrote:
>
> sorry have to say the bug still persists.
>

hmmm... that's odd.  I also noticed that in your screen snapshot, it looks 
like the overflow:visible
is causing the shifted content to spill outside of the tiddler.  Of course, 
this wouldn't be happening
if the transform:translateY(0px) was working.  *sigh*

In any event, I've also just made another update.  Now the 
AutoScroll/Viewer gets the scrolltime
value from the selected tiddler, instead of using an independent "duration" 
setting.  This makes
more sense since the scrolltime is now always related to the content being 
viewed.  Note that this
also means that, just like AutoScroll/Toolbar, changing the value modifies 
the scrolltime field of the
tiddler being displayed.  

I would assume firefox does something differently in the back compared to 
> chrome, but I currently can't think of what seeing how start to stop works, 
> but pause to stop does not.
>

Perhaps it has to do with how "pause" works.  It's not actually stopping 
the transform. Its just setting
the duration of the transform to 1000000000s (that's 1 BILLION seconds!).  
Even so, pressing "stop"
should set transform back to 0px with a speed of 0s.  I'm going to have to 
think about this a bit more,
but it might be "just one of those FireFox quirks" of which there are more 
than a few!

Thanks for testing the changes.  If you find anything else, please let me 
know.

-e

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/e2bbfab9-357d-44ac-9454-09f78a79500ao%40googlegroups.com.

Reply via email to