We tackled this in Bug 799615 for Send Tab -- we prefer to use the first link from the body, not the link to the tweet itself. Let's make sure we're using the same logic for the share handler. STR: * Open a tweet in the Twitter app. Make sure the body of the tweet contains a URL. * Share. * Choose "Save to Fennec". * Pick "Add to Reading List". * Observe that the added link is https://twitter.com/...

(In reply to Richard Newman [:rnewman] from comment #0) > We tackled this in Bug 799615 for Send Tab -- we prefer to use the first > link from the body, not the link to the tweet itself. The content of a Twitter share intent: android.intent.extra.TEXT: "Check out @TechCrunch's Tweet: https://twitter.com/TechCrunch/status/508045708638060546" "tweet_id": 508045708638060546 We are not sent the tweet body.

(In reply to Richard Newman [:rnewman] from comment #0) > We tackled this in Bug 799615 for Send Tab -- we prefer to use the first > link from the body, not the link to the tweet itself. Just to clarify: It looks like when you did Bug 799615 Twitter *did* send you the tweet body. They appear to have changed their behaviour :(

Ugh, Twitter.

I wouldn't spend too much time on trying to get the URL from the tweet body. This is sharing and sharing is non-standard payloads. However, should we decide to move ahead with adding similar overlay handling for OPEN/VIEW intents, this issue goes away. Tapping on the URL in the tweet (in Twitter) will get a similar OPEN handler in Firefox... should we decide to move ahead with that plan, and I hope we do.