Just confirming that embeds from Twitter are a problem for some users of certain browsers. They're invisible to me using Google Chrome v. 63.0.3239.132 under MacOS X 10.11.6 El Capitan (desktop installation).
• I also see the same problem in Firefox 54.0.1 with Basic Page Style enabled and no funny plugins or preferences
• The problem doesn't exist for Apple's Safari browser
• Ditto the mobile version of Chrome, it renders Twitter embeds just fine from an iPhone using WiFi to the same home network.
I didn't turn on Reader View or anything else that would suppress some page elements. I'm doing everything the same as I did before I stumbled on the issue, maybe ~10 days ago? Don't exactly know about the timing.
Post by Michael Stone on Jan 18, 2018 14:50:16 GMT -8
We've had multiple reports about this now but so far nobody has been able to link us to an embed that doesn't work or provide us with a replicatable test. I am running the same version of Chrome that you are and the tweets show up just fine for me. Have you tried private browsing mode to see if they display for you there?
At this point I'm completely confused. Could you check to see if you have any console errors that would indicate what the problem is? Hit F12 on a page where a tweet isn't displaying and copy all of that information into a post here.
Three things about that: (1) A couple of weeks back, 3rd-party cookie settings didn't seem to interfere with Twitter embedding; (2) Twitter embeds still work in Safari, where my cookie preferences setting has always been "Allow from current website only"; and (3) Letting just any 3rd party store a cookie on you is often called a bad, bad idea by people who pay attention to privacy and browser security... ?
tobase The settings I posted were for Chrome, which has a different setting altogether for disabling/enabling third party cookies which is different from the one I mentioned in my previous post. For twitter, try whitelisting https://platform.twitter.com
Here are the settings for FireFox for reference:
the exceptions screen:
I tested this and was able to view the embeds again.
For anyone trying to understand what's going on with 3rd party cookies and embedded info from Twitter, this is an educated guess.
Twitter won't let you have embedded tweets, unless your browser knows it's OK to exchange info in cookies with Twitter at platform.twitter.com.
— We know that, because as soon as you disallow 3rd party cookie exchanges, the tweets stop appearing.
But Twitter doesn't send your browser a cookie, simply because you asked to display an embedded tweet. — We know that, because when you look at what cookies you're holding, Twitter embeds work fine without any cookies that came from twitter.com.
That means, Twitter wants to *read* your browser cookies as a 3rd party, before it'll cooperate with your request to see embedded tweets.
– – – – – – – – – –
Different browsers take various approaches to this. If you haven't explicitly allowed 3rd party cookies in your browser settings, then:
• Firefox will not allow cookies to be read or sent by 3rd parties • Safari allows cookies to be *read* by 3rd parties, but not sent by them • Chrome… seems to have changed. It used to be like Safari, and now it acts like Firefox.
The Chrome Releases blog announced the rollout of a desktop update on January 4, about the time invisible tweets started happening around here. I don't see where anybody said anything about it, but I wonder if a related change wasn't made to Chrome at that time.