On Saturday, March 9, 2019 at 12:11:18 PM UTC+1, Mat wrote: > > ...AND it is actually possible to open the hosting TW from within the > iframe (i.e open the TW inside itself) and then make changes in the iframed > "copy" and save (using same file name of course)... and then refresh the > hosting TW to update and get the changes! >
So no misunderstanding: that saving is done INSIDE the iframe. Obviously, if you thereafter save the outer TW before the refresh, then the "iframed save" is overwritten. I'm guessing the nodejs version would avoid this restriction. Note that media queries, and maybe other techniques, could (probably) be used to sense if the wiki is presented as the outer TW or an iframed one so that e.g the save wiki button is shown in the iframe without need to scroll the iframe. The tiddlers could probably also be styled so that you only see the desired fields. BTW, if I recall, the current implementation of the editor actually has it in an iframe in native TW (but I'm not sure why). I'm thinking we should be able to take advantage of this and point the content of that TW to wherever we want. <:-) -- 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 https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/6b50f1b2-0daa-4c5c-8517-e47c0a9d7d5a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
