What steps will reproduce the problem?
1. Render a +1 button inside a container via pjax (basically
apis.google.com/js/plusone.js is only load on the 1st pageload)
2. mouse-over the +1 button, get the popup, mouse-out
3. click any other pjax enabled button
What is the expected output? What do you see instead?
everything works correctly on the page, in fact the snippet of code
$(document).on('pjax:complete', function() {
return gapi.plusone.go('plusone');
});
works correctly, but a long JavaScript exception is thrown and I can't catch
it. I am attaching the full error.
What version of the product are you using? On what operating system?
this does not seem be browser related, it happens on the development box (OSX
10.6, latest stable Firefox and Chrome) and when deployed to our private cloud.
I assume that the generated iFrame is re-rendered by
gapi.plusone.go('plusone'), but the initial API loaded still tries to reference
the previous dom#id? I am wondering if I'll have to invoke the full plusone.js
at every request as only solution
Please provide any additional information below.
the stack is ruby on rails and we're using pjax (pushState + ajax) to minimize
page load
error:
https://apis.google.com/_/apps-static/_/js/gapi/plusone/rt=j/ver=E-17J1RiS5c.en.
/sv=1/am=!vjVqvImSc8CICbuUGw/d=1/rs=AItRSTMxxXvuSCuNR6rRgdH3aKgP26p87g/cb=gapi.l
oaded_0
Line 41
it's INTERESTING that the issue does not occur if the user never triggers the
+1 popup.
Thanks
Original issue reported on code.google.com by etozz...@gmail.com on 18 Oct 2012 at 10:07
Original issue reported on code.google.com by
etozz...@gmail.com
on 18 Oct 2012 at 10:07Attachments: