HA! Your reply here and in a private email gave the missing piece in my 
puzzle of confusion; The plugin "Install" button is *not *in any iframe 
after all!

I'm sure some are rolling their eyes now because the whole process *has* 
already been explained several times, in hangouts by Jeremy. So let me 
explain why I never got it, in case anyone tries to explain it for people 
who might be as slow as I have been -* such as in potential documentation 
on the matter*:

It is the visual appearance of the plugin library and my perception of what 
an iframe is, that misled me;

Jeremy has (patiently) explained that the plugin library uses a hidden 
iframe and also a postMessage. Now, all use cases of iframes that I've seen 
are a visual representations of remote websites. So, the "deep digging" to 
reach the plugin list and the loading delay really tricked me into assuming 
that this involved the iframe, temporarily visible... or perhaps, somehow, 
not visible but still loading. I now understand that an iframe is not at 
all involved *before *you click the Install button and that an iframe is 
not *necessarily *a visual thing at all. Instead the click sets some 
parameter and it is only after this that the iframe - a separate matter 
(and styled to not display) - becomes active, and uses this parameter value.

So, NOW I think I finally got it (...but please do shout if I somehow still 
didn't...).

Big thanks!

<:-)

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" 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/tiddlywikidev.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/930c9e65-62a7-4ee0-b808-904abec8d9c7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to