1204934 - Polish transition to about:accounts from fresh load or first run load

Status: RESOLVED INVALID

(Firefox for Android Graveyard :: Firefox Accounts, defect)

Description

[Nick Alexander :nalexander [he/him]]

This is a general issue, exposed by the ways that about:accounts is often displayed.  On first run, say, a user that taps "Sign in to Browser" is likely to see:

* the first run screen;
* a tab bar with the generic globe icon and a grey content area -- shown while Gecko loads;
* a tab bar with the Firefox icon and a slightly different grey content background, with a Firefox-branded spinner or throbber -- shown while fxa-content-server loads;
* a smooth fade in to the fxa-content-server content.

This ticket tracks making the grey of the generic content area, of the loading spinner, and the fxa-content-server, match; possibly making the initial favicon match; and making the fade in smooth.

Comment 1

[Nick Alexander :nalexander [he/him]]

For the favicon and no-Gecko-loaded content area color, I wonder if we could include them as extras to the intent that launches Gecko with the about:accounts URI?  That might be interesting in more situations, actually: WebApps or other external consumers might want to give hints about content color.

mfinkle, have you heard this idea before?  Is there history about the grey loading background color I should know about?

Comment 2

[Anthony Lam (:antlam) Find me, @antlam on Slack!]

(In reply to Nick Alexander :nalexander from comment #0)
> This is a general issue, exposed by the ways that about:accounts is often
> displayed.  On first run, say, a user that taps "Sign in to Browser" is
> likely to see:
> 
> * the first run screen;
> * a tab bar with the generic globe icon and a grey content area -- shown
> while Gecko loads;

We should have this match the grey on the next screen (#F5F5F5).

> * a tab bar with the Firefox icon and a slightly different grey content
> background, 

I think we could use our "about header grey" here (#F5F5F5)

> with a Firefox-branded spinner or throbber -- shown while
> fxa-content-server loads;
> * a smooth fade in to the fxa-content-server content.
> 
> This ticket tracks making the grey of the generic content area, of the
> loading spinner, and the fxa-content-server, match; possibly making the
> initial favicon match; and making the fade in smooth.

I'll post more about the spinners, and fading perimeters later

Comment 3

[Nick Alexander :nalexander [he/him]]

For the record, right now our transition is not animated and flashes the home tiles screen (depending on load status, I assume).

Comment 4

[Nick Alexander :nalexander [he/him]]

Attachment: First.Run.Transition.to.FxA.mp4

Comment 5

[Mark Finkle (:mfinkle) (use needinfo?)]

(In reply to Nick Alexander :nalexander from comment #1)
> For the favicon and no-Gecko-loaded content area color, I wonder if we could
> include them as extras to the intent that launches Gecko with the
> about:accounts URI?  That might be interesting in more situations, actually:
> WebApps or other external consumers might want to give hints about content
> color.
> 
> mfinkle, have you heard this idea before?  Is there history about the grey
> loading background color I should know about?

Honestly, I don't have enough context to follow what you are trying accomplish. The video doesn't help either. As for putting extra information in an Intent, we could do that. Chrome has started experimenting with that for Webapps and Custom Chrome Tabs.

Comment 6

[Michael Comella (:mcomella) [NI reported issues only: ex-Mozilla]]

Bulk edit: moving potentially relevant issues from disabled Android Background Services product to Firefox for Android.

Removing priority to throw back to triage owners: please close these bugs if they're no longer relevant! Thanks!

Comment 7

[Mark Hammond [:markh] [:mhammond]]

This is no longer a thing.