Am 18.09.2014 12:59, schrieb Jeremy Ruston:
Can you reproduce the problem as a minimal test case with the stock
TiddlyWiki code? I'm afraid I don't have time to debug the additional
code in braintest at the moment.
Understandable. And this is not a TW5 bug, but rather a newtiddler
widget bug.
However, here is what happens there:
Danielo edited the newtiddler widget to clear the text field (set to
undefined) of the skeleton tiddler. Coincidentally the text field is
used to determine whether the tiddler is a skinny tiddler or not. So as
soon as the text field is cleared and a text reference to
"$:/temp/table" (the skeleton tiddler) is resolved (since the text field
of the skeleton tiddler is set to be the title of the new tiddler within
the newtiddler widget attributes), the core thinks this is a skinny
tiddler and tries to lazy load it.
This causes an 404 error which in turn creates an alert message. This
alert message is (surprise) a tiddler itself which triggers a refresh
event which causes the newtiddler widget to compute its attributes. And
since one of the attributes is the TextReference to "$:/temp/table"
(with text: undefined), it triggers the lazy load again which fails
again => alert message triggers refresh TextReference evaluation =>
triggers lazy load => ...
So I'm afraid Danielo, I think this should be fixed in your code.
(Suggested fix: set the text field to empty string)
/Andreas
--
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 post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.
