#1

Hi,

I recently came across this new issue.
twttr.widgets.createTweet() returned Promise is resolved very early, even before tweet is loaded completely.
I saw recently that embeded tweet are initially rendered with skeleton screens and actual content loads there after.

Promise is resolving too early, only skeleton is visible at that time and not the actual tweet.
I tried with by registering events also, But no luck.

twttr.events.bind("loaded", () => console.log("loaded"));
twttr.events.bind("loaded", () => console.log("rendered"));

Nothing seems to work. Is there a way by which we can know whether tweet is loaded/rendered fully ?

#2

Hi RealRonith,

Welcome to the community :slightly_smiling_face: and thank you for bringing this to our attention! May I ask for some context on how you plan on using this API and what you are looking to do with the information about whether a Tweet is loaded/rendered fully? We’ve made some changes recently that could be impacting the sequencing but want to make sure I understand what you are trying to achieve first so I can help you accordingly.

Thanks,

#3

Hi @gbalan0n
when tweet is fully loaded/rendered, I want to trigger some animation, transition then show them in a popup.
For all this I need to know when the tweet is fully loaded/rendered.

Thanks

#4

@RealRonith,

Thanks! I am looking into some things and will get back to you soon about this but in the meantime I am wondering does twttr.events.bind("rendered", () => console.log("rendered")); give you the same result?

#5

@gbalan0n

No, this was not working, last time I checked before creating this ticket.
If there are any recent changes, I can verify with latest version.

#6

Hey @RealRonith, I’m curious - what’s the animation/transition experience that you’re trying to create here?

#7

Hey @gbalan0n @RealRonith ,
I’m also facing an issue i.e. heightCallback is returning height 0, since the createTweet promise is failing due to missing target (document.getElementById(‘wrapper’)). Probably it’s related to the issue mentioned here.

#8

Hey imsanchit1995, thanks for sharing. We’ll look into this issue and see what we can find out

#9

Hey @RealRonith. We’ve rolled back a recent change in how the tweets are loaded while we re-evaluate the approach so your project might be back to its expected behavior. We’d love to hear more about your use cases and which parts of an embed lifecycle you hook into in addition to the tweet being rendered (creation, deletion, etc)?

#10

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.