On 5/25/07, Scott Sauyet wrote:
Sorry, I've looked at it a bit, and have absolutely no idea. It is very
strange. Sorry to have nothing to offer; I just didn't want you to feel
ignored. Good luck,
Thanks. :)
As I'm not familiar with the internals of Thickbox Reloaded, I've
added a dirt hack to make that example work: an extra parameter
'content' was added and I set $('#content') explicitly when
initializing it. Then inside Thickbox I check to see if content is
already set.
As someone pointed on the IRC channel, it seems that the #content box
is moved from dom to memory when the script starts, and then the
dynamically added thickboxes don't have it available anymore. I tried
but couldn't find in the code where this happens.
Another issue with Thickbox Reloaded is that, if you want to load a
iframed content which is on the same domain/port, you won't be able
because if it's on the same domain it will guess that you want ajax
(and this is not always true). I hacked it again to force an iframe
even when it's on the same domain, if a config is set.
Thanks again. If you think it is worth, I'll fill an issue to report these.
-- rodrigo
