Hmm, I don't think that moving content filtering the script elements
would be a good alternative, because of the processing costs... but
maybe removing all the script elements before calling the dialog
constructors would do the job, something near to what you proposed,
Edgar... I'll try it, too...
I think that the root of the problem, here, is the original API, that,
in my opinion, should implement different strategies of putting the
content in the document, because "document.write" is considered bad
practice if it can be avoided, together with the use of the "eval"
function. Aditionally, I think it would be nice if the reCaptcha
project opened the API source, so that we could write API bindings for
the various JS frameworks that we have (jQuery, Prototype, dojo,
MooTools etc). Open Source has proven to be a great regimen for small
or medium-sized projects to grow.
Nevertheless, the Ajax API use is working fine, for me, even though it
was not originally designed for non-Ajax use.
Regards,
Diogo
On Jul 31, 11:22 am, edgar klerks <
edgar.kle...@gmail.com> wrote:
> Dumb Idea, I can wrap my solution into an jQuery extension. Much less work.
>
> On Fri, Jul 31, 2009 at 4:18 PM, edgar klerks <
edgar.kle...@gmail.com>wrote:
>
>
>
> > Ah, I understand, why it goes wrong. Thought it was a bug in the browser.
>
> > I think it would be reasonable easy to extend jQuery with a method, which
> > doesn't use document.write but makes an new (script) element and adds it to
> > the dom. (with document.createElement)
>
> > You can check the script element already exists in the dom, so it won't be
> > added twice.
> > I am on holiday now, but I will give it a try when I am at home again.
>
> > Greets,
>
> > Edgar
> > On Thu, Jul 30, 2009 at 7:42 AM, diogobaeder <
diogobae...@gmail.com>wrote:
>
> >> I'm new here, but I'd like to discuss about this issue because I'm
> >> having the same problem.
>
> >> As you can see here:
>
> >>
http://groups.google.com/group/jquery-dev/browse_thread/thread/0acd28...
> Email:
Edgar.kle...@gmail.com,