Callback after twttr.widgets.load processes tweets on the page

benward · 2012-12-11T02:21:17.000Z

There’s nothing like that just yet, I’m afraid, but that’s a nice addition to make. I’ll take a look into it.

For now, you might get some milage by watching for DOM mutation events in newer browsers (although that whole API is unstable and being replaced in DOM4, so ymmv), but our initialization code will run replaceChild on all the embed codes with their iframe replacements, so you might be able to use it still.

As I say, we’ll look into giving you a proper callback interface soon.

mitar_m · 2012-12-11T02:39:27.000Z

Yes, watching DOM changes is … ugly. At least for now. I will wait for better interface. Thanks! You are really great and responsive.

mitar_m · 2012-12-11T02:55:02.000Z

Ah, one more thing. It would be great if callback would get information if tweet existed. Currently, I cache html fragment for the tweet and then call twttr.widgets.load over those fragments. If tweet was deleted in meantime, fragment is left as it is. It would be useful to get this information in callback so that I can decide what to do (probably simple remove the tweet and inform the server to check).

mitar_m · 2012-12-11T05:32:32.000Z

Or even better. As Twitter library fetches data about tweets from the server, this data could be passed to the callback. If data would be missing, this means tweet was deleted. If data would be there, developer could use this for example to provide a feedback for current number of retweets (for example, add some CSS to show more popular tweets).

mitar_m · 2013-01-12T01:52:58.000Z

Any followup?

seagyn · 2013-06-14T09:18:57.000Z

+1 on this.

Kenjamin · 2013-10-07T18:34:09.000Z

+1 Would love to see this too

BoolaDev · 2013-10-24T18:10:29.000Z

+1

pepsilike · 2013-10-29T12:18:37.000Z

+1

MrLugh · 2013-12-16T05:42:37.000Z

Hey guys! Any progress about calling a callback after tweets are loaded?

somethin_better · 2013-12-16T14:22:39.000Z

I ended up loaded tweets ‘dynamically’ from my own database so in that instance, callbacks are your own responsibility, this can also cut down on twitter calls, but is slightly less than ‘real-time’.

After a year and 5 days, this probably won’t be resolved helpfully anytime soon…

good luck!

bartknows · 2013-12-29T19:04:38.000Z

+1 for this…

anirban_dutta_ · 2014-01-02T07:02:00.000Z

Hi, I have a problem where the Twitter widget gets hidden because my website cannot handle the within the iframe, so the embedable timeline widget looks like:

However it does not work because the resizeMe callback must be called after twitter gets finished with it’s execution (and sets the size), within the iframe. They said " For this, you must set up the twitter feed to make the callback after it is loaded. Typically this is done by using the ready function." - Has anyone faced this problem? Any idea how to make this work?

sduncombe · 2014-01-19T21:51:00.000Z

How I solved this - use DOMNodeInserted or DomNodeRemoved events.

JS Fiddle: http://jsfiddle.net/mojowen/9x3bh/

mitar_m · 2014-01-19T22:04:00.000Z

Those events are deprecated. https://developer.mozilla.org/en-US/docs/Web/Guide/Events/Mutation_events

ninjaPixel · 2014-06-19T01:14:00.000Z

+1 for this feature, too

benward · 2014-06-20T20:12:00.000Z

Hi everyone. Since this thread happened we added two new events. Use twttr.events.bind(‘rendered’, ƒ) to get an event for every individual widget that renders in a page, or twttr.events.bind(‘loaded’, ƒ) for the whole set after you call twttr.widgets.load.

See the [node:25877, title=“scripting events documentation”] for more details.

Ben

ninjaPixel · 2014-06-21T17:18:00.000Z

Thanks, Ben!

shotbyjosh · 2014-07-07T21:47:10.000Z

can you please post your code for this? i’m trying to do the same thing…

shotbyjosh · 2014-07-07T21:48:57.000Z

to clarify i’m talking about the infinite scrolling, and reloading the page