782442 - Be able to activate social api from mozilla.org

Status: RESOLVED INVALID

(Firefox Graveyard :: SocialAPI, defect)

Description

[Shane Caraveo (:mixedpuppy)]

need to implement support for activating from internal content.

Comment 1

[Jared Wein [:jaws] (please needinfo? me)]

To be clear, support for this exists already if we redirect users to a special page on the providers site.

This bug is to track getting third parties to implement a page that triggers activation.

Whether we want to ask providers to implement a page that triggers activation is probably a bigger question. I've flagged this bug for sec-review-needed to answer this question.

Comment 2

[Curtis Koenig [:curtisk-use curtis.koenig+bzATgmail.com]]]

We need more information before we can answer this, will file a bug in our component with needed info blocking this bug.

Comment 3

[Curtis Koenig [:curtisk-use curtis.koenig+bzATgmail.com]]]

setting this one to - until we get more information

Comment 4

[Laura Forrest]

Here's more clarity, let me know if questions: 

We want to be able to enable users to turn on the social API from a page on mozilla.org in order to essentially give them a way to turn it on without having to rely on a partner. Perhaps this is a matter of whitelisting, I'm not sure, but here's a user story:

Jane hears about the Social API from a article on TechCrunch and wants to learn more and try it out. She clicks on the link within the article and lands on a marketing landing page hosted on Mozilla.org that shows her a overview, a cool video of it in action, and contains a big button to 'get started now'. When she clicks that button the side panel pops up, she provides her login credentials and is now using the social api.    

This button need only support one social provider at a time. Let me know if there are questions.

Comment 5

[:Gavin Sharp [email: [e-mail]]]

I don't think we need to track this here - provider activation is already supported in the client (bug 764869), and we've decided that for activation-from-mozilla.org we can rely on the providers to give us a way to do that (embedded iframe with postMessage API of some sort). To track that on our end, we'll probably want a webdev bug for mozilla.org, and we'll need to coordinate with the providers.

Comment 6

[Laura Forrest]

Adding Chris More and Mike Alexis to help get what we need from the WebDev team. I've filed a bug here to track: 790455.

How can we make sure our provider provides this? I'm sure WebDev needs code from them. Would that entail a separate on Asana? I'd hate for this to fall into the cracks.

Comment 7

[Laura Forrest]

(In reply to Laura Forrest from comment #6)

* Typo -- meaning a separate "bug" on Asana 

> from them. Would that entail a separate on Asana?

Comment 8

[Chris More [:cmore]]

Please keep the Web Productions team updated on the status on the provider code. You can ping us in #webprod on IRC or [e-mail].