Matthew A. Miller

@m8ttyB no it does not.

Staging deployed: * URL == https://kinto-lockbox.stage.mozaws.net/v1/

> @linuxwolf @sashei do you two have corresponding sub-tasks or issues opened for the extension (datastore?) and iOS app to track the exploration and OAuth work yet so we can...

@devinreams we'll get it sorted out in our sprint planning.

@changecourse @sandysage see https://github.com/mozilla-lockbox/lockbox-extension/issues/534#issuecomment-367502065 for questions/concerns before engineering can scope.

to have a good starting search term, some (unrefined) thoughts on origins: https://gist.github.com/linuxwolf/5722b60907826b47a97b10cf36676ca2

@changecourse Some comments and questions: * Is it safe to assume the "trigger" for onboading is the same as it is today? (e.g., on install, or when clicking the toolbar...

@iamVP7 did you happen to capture a screenshot of the failure state?

(regarding multiple matches) @changecourse something to keep in mind, although I don't know if/when it'll be an actual problem: an overlay would have to be "in content", which means it...

@changecourse I agree it's an edge case, and a very thin edge at that. This will need to be taken into account by @mozilla-lockbox/product-integrity and testing as a known risk.