bugzilla.mozilla.org has resumed normal operation. Attachments prior to 2014 will be unavailable for a few days. This is tracked in Bug 1475801.
Please report any other irregularities here.

Get design for sync login/status widget

RESOLVED INVALID

Status

Web Apps
AppsInTheCloud
P3
normal
RESOLVED INVALID
7 years ago
6 years ago

People

(Reporter: ianbicking, Unassigned)

Tracking

Details

(Whiteboard: client [nonmwcblocker])

(Reporter)

Description

7 years ago
In the HTML dashboard with the HTML repo, the login and status functionality is embedded in an iframe.  We need some fixed-space layout for sync that can express a couple states:

* You need to log in (probably just a BrowserID login button)
* You are logged in, displaying status in a compact form:
  - sync is working
  - sync has had some problem
  Probably detail here is no necessary or feasible
* An expanded status; currently I have implemented it so the iframe can expand in-place.  This probably should display:
  - Who you are logged in as
  - Logout
  - Status messages, if any (typically errors, as well as simply being offline)
  - Force sync now?
  - Maybe account management(?) - I'm not sure what this is, and what the dashboard can do itself, but some features like deleting your sync account need some kind of home.

The design should be such that it isn't jarring when embedded into another site (the dashboard).  I've allowed for some configurability (e.g., background colors, button colors).

The current layout is in the openwebapps repository, /site/jsapi/syncbutton.html (this is just a placeholder design), and is currently developed on the feature/sync branch but may move to develop.
(Reporter)

Updated

7 years ago
Priority: -- → P3
(Reporter)

Updated

7 years ago
Whiteboard: client
A Pivotal Tracker story has been created for this Bug: https://www.pivotaltracker.com/story/show/24808867

Updated

7 years ago
Whiteboard: client → client [nonmwcblocker]
The old app sync codebase is no longer going to be supported. Apps in the cloud will be under a different codebase. None of these bugs are valid anymore.
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.