Great to wake up and find that the problem was tracked down. Thanks, gang! Meanwhile, I wonder about any Chrome-using newbies who might have downloaded the same empty.html (with the corrupt "Using ... node.js" tiddler) and become simply discouraged that some of their work seemed to disappear into the void.
(At least twice I tried a restore from tiddlyspot backup while I was trying to find recent tiddlers I had a vague memory of having created... In my case, my first assumption is usually that because of work and home computers I must have left a tab open, failed to reload, and mistakenly allowed new edits to override work from the other location.) In all my years of working with TW, I have managed to screw up my own UI by tinkering above my competence, and have also come across problems introduced by plugins, but have never before had something fail for a reason that wasn't, in some sense, traceable to my own missteps. Isn't it fascinating that the timeline macro, faced with a corrupt tiddler, would show a corrupted sort-order in Chrome, but not in other browsers? -Springer On Saturday, May 23, 2020 at 5:53:00 AM UTC-4, Mat wrote: > > Ah, you're right. Removing that tiddler also corrects the timeline. > Highlight a brittleness in the timeline macro tho. I'm closing my issue > because I don't know how to best describe the problem.Thanks Saq. > > <:-) > -- 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 tiddlywiki+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/2802e8a0-6ee2-4cac-a902-1e1a19439ed1%40googlegroups.com.
