It would be nice if in addition to twttr.ready() there was a twttr.notReady(), or some other event that would fire when https://platform.twitter.com/widgets.js is never going to function.
This is in relation to the deprecation of support for IE. I think that the library tests /(MSIE ([6789]|10|11))|Trident/.test(navigator.userAgent) and never does anything when loaded in a browser that matches this UA. I’d love it if the JS could directly inform me of this so that I can deal appropriately with the lack of a feed on the page. Instead right now I’m waiting three seconds and checking whether the <a class="twitter-timeline"> has been removed, and if not, informing the user.
https://twittercommunity.com/t/widgets-on-ie11/133450
A7rRay
#2
Hey @bogosian
Thanks for your request. We will take that into consideration. I am not sure exactly what your use-case is, but if it is styling it is common to style the blockquote however you prefer and that styling will persist after a failure to load.
With the default timeline embed code the anchor tag element is visible on the page until widgets.js is processed and finds the tag, replacing it with the iframe - this causes a brief flash on the page for non-IE browsers of whatever text is inside the anchor. For IE users, the anchor text stays, which is fine, however I’d prefer to be able to have more descriptive text available to the user explaining why they aren’t seeing a timeline - and using the default embed code the only way to do that is to put all of that descriptive text in the anchor, making it clickable.
What I’m looking for is a more deterministic approach - preferably a single empty div element I can target with JS that is either replaced by the Twitter iframe, or is replaced by arbitrary HTML that I can inject when the .notReady() event fires.
system
closed
#4
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.