Embedded Timeline not rendering in Internet Explorer


Today our embedded timeline stopped working in Internet Explorer 11. This is an internal intranet page so i can’t share the url. This is a basic twitter-timeline embed. I don’t see any console errors and the page will work in chrome and firefox. The last request in a fiddler trace is widgets.js in IE and for chrome it proceeds past that request. Any help is appreciated. Thanks.


Hi @joe_reichard,

I’m unable to reproduce this issue. Can you provide the embed code for the timeline? Or possibly test to see if it renders correctly on publish.twitter.com?



I have the exact same issue. We are using IE11 (Document mode 10). Intranet so can’t provide the URL
Embedded timelines were working on Friday but have stopped since then.

  • The widget script was the standard output created using the tool at publish.twitter.com
  • If I switch IE to Document mode 11 then the timelines will load, unfortunately we currently need to remain in Document mode 10.
  • I can also confirm it still works in Chrome and Edge
  • Has anything changed that would prevent the timelines loading in Document mode 10?


Hi @joe_reichard and @Daveyskills1977,

Thanks for the additional info. I was able to reproduce this issue by running IE 11 with “Document Mode” set to IE 10. This essentially causes the browser to act as IE 10.

We recently announced that we won’t be supporting IE 9 and IE 10 anymore, and I believe that change is what is causing widgets not to render on your pages.

To fix this, you can try to load your page without using IE 10 compatibility mode. This could be caused by a browser setting, or by an HTML tag like <meta http-equiv="X-UA-Compatible" content="IE=10" /> on the site you’re visiting.

I hope that helps!


Thanks for the update, I was assuming this was the case.
I understand that SharePoint 2013 is set to use document mode 10 by default so you may see a number of queries along these lines!

Thanks again.


SharePoint 2013 indeed needs the meta http-equiv=“X-UA-Compatible” content=“IE=10” to be set in order to work with Internet Explorer browsers. It’s in the out of the box master pages and removing it breaks core functionality of SharePoint in Internet Explorer. Microsoft says edge mode (the latest) is not support in SharePoint 2013 (see here: https://docs.microsoft.com/en-us/sharepoint/install/browser-support-planning) so the tag has to stay on SharePoint 2013 sites. Does this mean no more embedding Twitter feeds in SharePoint?



As stated earlier, SharePoint 2013 indeed contains the meta http-equiv=“X-UA-Compatible” content=“IE=10” within the Master Pages. So it would be unwise to remove the tag from the Master Pages.

Could you please provide a workaround for SP2013 and IE11 as we have a number of embedded feeds on the company Intranet, which have recently stopped working?

Or, do we just reside to the fact that the functionality of embedding Twitter feeds in SP2013 is long gone?




We are also having same issue in SharePoint 2013 environment. Do you have any updates on this please?


Thanks for the feedback here. We recognise that this is inconvenient for some users.

We don’t have any plans to build in a workaround for this specific use case - Microsoft announced the end of life for Internet Explorer 9 & 10 as January 2016, and while this incompatibility is unfortunate for this specific case, unfortunately our embedded timelines will no longer work and cannot be used in browsers operating in IE 10 document mode as we invest in ongoing improvements to support modern web standards.

For further information, please refer to Microsoft’s documentation on older versions of Internet Explorer and their lifecycles.


Same issue for us on SharePoint 2013 with IE 11.


Hello Andi,

thanks for the response.
The Problem is, that SharePoint does not support Edge Document Mode fully. Officially yes, but in edge mode Active-X is not working:

We have IE 11 in 10 document mode for SharePoint 2016. And it is of course not working :frowning:

I also tried a html page with the meta tag from above and then add it as iframe, but it also does not work.

Does anyone has some workaround?


This guy has a fix for the issue that works for me - https://www.koskila.net/2018/05/18/how-to-fix-twitter-embed-in-sharepoint/#cerber-recaptcha-msg


Wow, thanks Lumpygroovy, this really works for me too.
Unfortunately it destroyes some custom javascript code of me, for the suitebar :frowning:

But on his site is also a small mistake:
The closing script () must be before the link part.
Such way it is correct:

<!-- the Twitter a-element and the platform/js code goes here -->
<script async src="https://platform.twitter.com/widgets.js" charset="utf-8">


Yes, that’s right, forgot to mention that. You have to close the block he supplies before you add the usual twitter anchor and twitter script link after it.


Have some problem with custom code for the suitebar :frowning:
But usually it will work.

If anyone has problems with custom javascript code and this solution from Lumpygroovy.
Just create a html page with only the solution in it and then add a site viewer webpart to your homepage or where ever you want it, which points to this new html page.


I’ve come in this morning and our embedded twitter feeds are now working again on SharePoint 2013. Has anyone else noticed this? Has Twitter rolled back the changes? If so, how long will this be for?


I can not confirm this. I tried it now on our development environment and it is still not working.


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