Skip to main content

Google Plus One button callback - Any way to "subscribe" to the +1 action?


I'm looking for a way to subscribe to the plus one button.



According to the documentation here: https://developers.google.com/+/plugins/+1button/#plusonetag-parameters I could add a callback attribute to the tag, but in my case I'm not allowed to interfere. I'm building a tool ontop of the site, an embedded JS triggered on document ready. I want to add the callback live, and it mustn't interfere the original callback if one was declared.



I don't have this problem with Facebook or Twitter (like and tweet, for instance) . In these cases there's the FB and twttr global variables, registered like so once they are available:




FB.Event.subscribe("edge.create", function(e) {
console.log(e);
})



or twitter's twttr.events.bind ...



Am I missing anything or is Google choosing a very awkward way to do things? What's their interest in this method and what can be done around it?


Source: Tips4allCCNA FINAL EXAM

Comments

  1. You can use the JavaScript API to retrieve the +1 callback.

    gapi.plusone.render(
    myDomNode,
    { "callback": myCallbackFunction });


    Or you alternatively can specify the "callback" attribute if you're using the DOM version.

    In either case, the callback will be invoked with an object which has two properties: href returns the URL which was +1'd, and state is either "off" or "on".

    ReplyDelete
  2. You could go one further than Daves answer, and indeed inject your own callback - but take the extra step of retrieving the existing callback value beforehand and dispatching it yourself within your own handler (if there is an existing callback value) with the same values as your callback received.

    That way both your handler and the original handler will be called, and hopefully no one would be any the wiser :)

    ReplyDelete
  3. An aggressive but usually workable solution would be to replace the callback attribute of the G:PLUSONE tag with your own function, which can call the original callback (if one was defined) and do its own stuff, too. Google's plusone.js script replaces the G:PLUSONE tag with an iframe, so this has to be done before this script executes (probably with a DOM-ready hook). Here's a naive example (which you can see working on jsfiddle - open up a debug console and click the +1 button).

    <head>
    <script src="http://ajax.googleapis.com/ajax/libs/jquery/1.7.1/jquery.min.js"></script>
    <script>
    var originalCallback = function(o) {
    console.log('original callback - ' + o.state);
    };
    // on DOM ready
    $(function() {
    var plusoneTag = $('G\\:PLUSONE');
    var originalCallbackName = $(plusoneTag).attr('callback');
    // global function
    hijackerCallback = function(o) {
    console.log('hijacking callback - ' + o.state);
    window[originalCallbackName](o);
    };
    plusoneTag.attr('callback', 'hijackerCallback');
    });
    </script>
    <script type="text/javascript" src="https://apis.google.com/js/plusone.js"></script>




    ...persume that somewhere in the host page you have the +1 tag, like so:

    <g:plusone annotation="inline" callback="originalCallback"></g:plusone>


    As a side note, I've tried to listen for the removal of the G:PLUSONE tag using DOMNodeRemoved and replace the callback then - but that's too late and the plusone.js script is already bound to the original callback at this stage. In the real world, you should probably try injecting your script just before plusone.js (we're probably talking about a Chrome or Firefox extension here).

    ReplyDelete

Post a Comment

Popular posts from this blog

[韓日関係] 首相含む大幅な内閣改造の可能性…早ければ来月10日ごろ=韓国

div not scrolling properly with slimScroll plugin

I am using the slimScroll plugin for jQuery by Piotr Rochala Which is a great plugin for nice scrollbars on most browsers but I am stuck because I am using it for a chat box and whenever the user appends new text to the boxit does scroll using the .scrollTop() method however the plugin's scrollbar doesnt scroll with it and when the user wants to look though the chat history it will start scrolling from near the top. I have made a quick demo of my situation http://jsfiddle.net/DY9CT/2/ Does anyone know how to solve this problem?

Why does this javascript based printing cause Safari to refresh the page?

The page I am working on has a javascript function executed to print parts of the page. For some reason, printing in Safari, causes the window to somehow update. I say somehow, because it does not really refresh as in reload the page, but rather it starts the "rendering" of the page from start, i.e. scroll to top, flash animations start from 0, and so forth. The effect is reproduced by this fiddle: http://jsfiddle.net/fYmnB/ Clicking the print button and finishing or cancelling a print in Safari causes the screen to "go white" for a sec, which in my real website manifests itself as something "like" a reload. While running print button with, let's say, Firefox, just opens and closes the print dialogue without affecting the fiddle page in any way. Is there something with my way of calling the browsers print method that causes this, or how can it be explained - and preferably, avoided? P.S.: On my real site the same occurs with Chrome. In the ex