Edit this page

Known Limitations

This article lists the known limitations of the RadSocialShare control.

Tweet Event of a Twitter Button is not Fired Under IE

When the end user posts their Tweet on Twitter, their scripts should return this information to the originating page. The Example 1 will show an alert when this happens. This event is not raised in IE. Example 2 shows how to reproduce this issue with the pure HTML code Twitter provide. Until it is fixed officially, RadSocialShare cannot raise the event, because it depends on the scripts coming from Twitter.

Example 1: Twitter does not raise the Tweet event with RadSocialShare.

<telerik:RadSocialShare RenderMode="Lightweight" runat="server" ID="RadSocialShare1" OnTweet="OnTweetHandler">
    <MainButtons>
        <telerik:RadTwitterButton />
    </MainButtons>
</telerik:RadSocialShare>
<script>
    function OnTweetHandler(sender, args) {
        alert("OnTweetHandler");
    }
</script>

Example 2: Pure HTML code from the Twitter website that shows the same issue.

<a class="twitter-share-button"
    href="https://twitter.com/share"
    data-url="https://dev.twitter.com/web/tweet-button"
    data-via="your_screen_name"
    data-text="Checking out this page about the Tweet Button"
    data-related="twitterdev:Twitter Developer Relations"
    data-count="vertical">Tweet
</a>

<script type="text/javascript">
    window.twttr = (function (d, s, id) { var t, js, fjs = d.getElementsByTagName(s)[0]; if (d.getElementById(id)) { return } js = d.createElement(s); js.id = id; js.src = "https://platform.twitter.com/widgets.js"; fjs.parentNode.insertBefore(js, fjs); return window.twttr || (t = { _e: [], ready: function (f) { t._e.push(f) } }) }(document, "script", "twitter-wjs"));

    twttr.ready(function (twttr) {
        // Now bind our custom intent events
        twttr.events.bind('tweet', tweenEvent);
    });

    function tweenEvent(event) {
        alert(event);
    }
</script>

The example above is extracted from https://dev.twitter.com/web/javascript/events and has been amended.

You can read more about this problem in the Twitter Community Forums:

See Also