Great tip, I managed to solve my problem described in
http://groups.google.com/group/recaptcha/browse_thread/thread/8dc383428edad9ba
with these "instructions" and with some explanations in
http://groups.google.com/group/recaptcha/browse_thread/thread/0f24dff9c30d597c
- at least it seems to work now, let's see if it stays that way.
A suggestion to including Recaptcha.create after page loading -
instead of a timeout it would probably be better to include it in body-
onload or in my case with Prototype the statement
"document.observe("dom:loaded", function()
{ Recaptcha.create(...); });" is perfect, it loads Recaptcha right
after the DOM has been loaded so page and reCAPTCHA creation even
feels faster than doing it the non-AJAX way.
I think in my case reCAPTCHA conflicted with Prototype, because the
problem disappeared as soon as I did not include either Prototype or
reCAPTCHA - I think there should be a Prototype-compatible out-of-the-
box-version of reCAPTCHA and/or some kind of information about this
possible problem in the documentation, because it's hard to actually
notice the problem and find any solution for it - it took me 2 weeks
to just notice the problem and another 2 weeks until I found this
thread and the other one which at least discuss the problem - that's
quite a bad "user" experience for me, and I'm still weary if it
actually works now. It seems this problem can be caused by different
JS libraries, so a warning would be good as long as no fix is
available.
Is there any kind of official fix coming in the near future?