Closed
Bug 1203323
Opened 9 years ago
Closed 9 years ago
share plane can't post to twitter
Categories
(Firefox Graveyard :: SocialAPI, defect)
Firefox Graveyard
SocialAPI
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1188378
People
(Reporter: blassey, Unassigned)
Details
This has been happening for a while. When I click on the share plane I get:
(!) Nightly is unable to connect with Twitter right now.
There's nothing in the browser console
Comment 1•9 years ago
|
||
It's working fine for me so I'd need some further debugging from you to understand what it may be.
I've seen this in the past at times when some resource loaded by the page gives a 404. The error handler is a bit obnoxious in showing the error page for *any* error. Do you see any 404 errors via the browser console?
If you load the tweet intent, https://twitter.com/intent/tweet/ in a tab and do a force refresh, does it fix the issue?
Comment 2•9 years ago
|
||
I can confirm this issue here (Firefox 41.0 stable on Arch Linux x86_64).
I have no problem loading the Twitter intent page (yes, with a force refresh), but I can't load it in the share panel (unable to connect).
I wrote a simple share service ( https://github.com/Hexcles/socialapi-fanfou/blob/master/index.html ) for a Chinese SNS using the Social API before and I'm now experiencing the same unable-to-connect problem in that service too. Since that particular SNS is not HTTPS, I used WireShark to see what exactly is being sent and received by Firefox. It seemed to me everything is fine: the request was as expected and the response was the desired share widget page with status code 200. Yet Firefox still said "unable to connect".
FYI, Facebook and G+ sharing is working fine. Tumblr is also broken. I've tried cleaning the cache, re-installing the services, but it didn't help.
I'm willing to help debugging this issue. Tell me if I can provide any useful information.
Comment 3•9 years ago
|
||
Do you have any extensions enabled? If so disable them and see if that fixes the issue. If it does, maybe you can narrow down which addon is the issue.
Comment 4•9 years ago
|
||
(In reply to Shane Caraveo (:mixedpuppy) from comment #3)
> Do you have any extensions enabled? If so disable them and see if that
> fixes the issue. If it does, maybe you can narrow down which addon is the
> issue.
I created a new profile and played around a little while. I think I found the root cause: Tracking Protection.
In a clean profile, after I turned on privacy.trackingprotection.enabled and restarted Firefox, sharing to Twitter/Tumblr broke. If I turn it off, sharing to Twitter/Tumblr works again.
Obviously it has something to do with the off-by-default tracking protection.
Comment 5•9 years ago
|
||
Interesting, but with tp turned on, you're able to load the intent url for twitter in tab but not in the share panel?
I think this would be a dup of bug 1188378
Comment 6•9 years ago
|
||
Yes that's exactly the same issue! The weird thing is that: 1. I can open Twitter without problems; 2. I can open and share to Facebook in that panel without problems; 3. I can't share to Twitter...
I guess you can close this one as dup.
Comment 7•9 years ago
|
||
Can you specifically open the tweet intent in a tab without a problem when tp is enabled?
https://twitter.com/intent/tweet/?url=http://www.mozilla.org
Flags: needinfo?(bob1211)
Comment 8•9 years ago
|
||
Affirmative. Although I got several CSP errors and a tracking protection block (see https://pastebin.mozilla.org/8848191 for logs), the link opened and displayed without problems. I also tried opening the link with tracking protection disabled. All the CSP errors were still there, but no more tracking protection message.
Hence, I'm wondering if the tracking protection block is somehow considered as an "error" by the social panel, so it shows "unable to connect". The CSP errors don't seem to be related here, since when TP is disabled, CSP errors still appear and social sharing works just fine.
Flags: needinfo?(bob1211)
Updated•9 years ago
|
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
Updated•6 years ago
|
Product: Firefox → Firefox Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•