Re: Problem with new reCAPTCHA in a single-page AngularJS app

This doesn't solve the problem which original post describes.Dorian Karter於 2014年12月11日星期四UTC+8上午6時01分37秒寫道： You guys should try this out: http://bit.ly/12Qdp2J Wednesday, December 10, 2014 8:34:48 AM UTC-6, Thomas Deater wrote: We used this reCAPTCHA directive as a starting point, but have modified it extensively: http://bit.ly/1Dcy9CR Wednesday, December 10, 2014 8:35:49 AM UTC-5, Arif Setiawan wrote: Hi Thomas, can you share how to implement new recaptcha on angularjs? because i've struggling for hours with no luck, thanks before :)On Wednesday, December 10, 2014 5:11:57 AM UTC+7, Thomas Deater wrote: We are building a multi-step registration flow as a single-page AngularJS app. There is a reCAPTCHA on step 1. When the user successfully submits that form, we destroy that view (including the reCAPTCHA element and iframe) and render step 2. However, there appear to be various event-bindings related to reCAPTCHA that are left on the page, which results in multiple errors being logged to the console each time the user clicks any element in step 2: Uncaught SecurityError: Blocked a frame with origin "http://bit.ly/1eCg7Yn" from accessing a frame with origin "https://foo.com". Protocols, domains, and ports must match. I think the new reCAPTCHA really needs a destroy() method (like the old reCAPTCHA) to clean this up. -- You received this message because you are subscribed to the Google Groups "reCAPTCHA" group. To unsubscribe from this group and stop receiving emails from it, send an email to recaptcha+unsubscribe@googlegroups.com. To post to this group, send email to recaptcha@googlegroups.com. Visit this group at http://bit.ly/1dkFnYd. For more options, visit http://bit.ly/P65DvS.