Jed Parsons (use needinfo, please) [:jedp, :jparsons] Reporter
	Description • 12 years ago

In order to implement the payment and identity flows for basecamp, navigator.id needs a trusted UI.

There is already a requirement for a trusted UI for mozPay, and the consensus appears to be that, for v1 at least, it will not be possible to make a generalized trusted ui api that would be available to native services like mozPay, id, etc.

We are fine with copy-and-paste solutions.  But in the end, the flows require a UI for nav.id that looks and acts exactly like the one for mozPay, and provides a way for us to message to and from the native nav.id code.

mozPay trustworthy UI: #768943

	Jason Smith [:jsmith]
	Comment 1 • 12 years ago

Is this a Gaia or Platform bug? It feels Gaiaish.

	Jason Smith [:jsmith]
	Comment 2 • 12 years ago

See also https://github.com/mozilla-b2g/gaia/issues/2580.

	Jason Smith [:jsmith]
	Comment 3 • 12 years ago

Migrated to Gaia GitHub - https://github.com/mozilla-b2g/gaia/issues/5323, as this is a front-end feature.

	Caitlin Galimidi [:c8o]
	Comment 4 • 12 years ago

Keeping this bug for project tracking purposes only. 
Developer details and technical requirements in github.

https://github.com/mozilla-b2g/gaia/issues/5323 (assigned to Fernando on the Gaia team)

	Jason Smith [:jsmith]
	Comment 5 • 12 years ago

I'd really prefer that we talk this out before you take action, as there's ways we can figure out tracking. But this is still not valid as it stands right now.

	Jason Smith [:jsmith]
	Comment 6 • 12 years ago

Okay, per talking with dietrich, all feature tracking that is v1 also needs to be in bugzilla. Moving this to Gaia in bugzilla and reopening.

	Jason Smith [:jsmith]
	Comment 7 • 12 years ago

My apologies for any confusion ferjm that this massive bug churn looks like. So 10/1 and after, they want any v1 tracking done in bugzilla. I'm closing the github issue, migrating the info to here, and starting tracking here.

	Ben Adida [:benadida]
	Comment 8 • 12 years ago

This bug's scope is limited to making the existing popup UI "trusted."

	Lucas Adamski [:ladamski]
	Comment 9 • 12 years ago

Fernando, how is this coming along?

	Fernando Jiménez Moreno [:ferjm]
	Comment 10 • 12 years ago

(In reply to Lucas Adamski from comment #9)
> Fernando, how is this coming along?

No work done so far. This is blocked by Bug 794680. Once that one lands, this bug should be trivial to implement. It should only be a matter of using the TrustedUIManager instead of the PopupManager as it is currently used in https://bugzilla.mozilla.org/attachment.cgi?id=667617&action=diff#a/apps/system/js/identity.js_sec2

	Ben Adida [:benadida]
	Comment 11 • 12 years ago

Fernando: I think Zach Carter on my team can handle this if you'd like, following your example on nav.pay, since he's also writing the identity Gaia tests. What do you think? Now that you've created the example, as you say it should be easy :)

Plus, this means one patch, instead of two.

	Fernando Jiménez Moreno [:ferjm]
	Comment 12 • 12 years ago

Sounds good.

	Jason Smith [:jsmith]
	Comment 13 • 12 years ago

Per today's b2g meeting - at risk features do not block ship. Renoming.

	Jason Smith [:jsmith]
	Comment 14 • 12 years ago

(In reply to Jason Smith [:jsmith] from comment #13)
> Per today's b2g meeting - at risk features do not block ship. Renoming.

Ignore my comment here. This was a point of confusion on my part.

	Mike Connor [:mconnor]
	Comment 15 • 12 years ago

Restoring blocking flag.

	Zachary Carter [:zaach] Assignee
	Comment 16 • 12 years ago

PR awaiting review: https://github.com/mozilla-b2g/gaia/pull/5854

	Fernando Jiménez Moreno [:ferjm]
	Comment 17 • 12 years ago

(In reply to Zachary Carter [:zaach] from comment #16)
> PR awaiting review: https://github.com/mozilla-b2g/gaia/pull/5854

I've attached the PR to Bug 794680 and ask for r? to Vivien.

	Zachary Carter [:zaach] Assignee
	Comment 18 • 12 years ago

Closing. See Bug 794680.

	Jason Smith [:jsmith]
	Comment 19 • 12 years ago

Talked to Zach about this in b2gpay - duping instead.