Closed Bug 1102395 Opened 11 years ago Closed 8 years ago

[FxA] Tapping a "Create account or sign in" button causes transition issues before a requested page is loaded

Categories

(Firefox OS Graveyard :: FxA, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(blocking-b2g:-, b2g-v2.0 affected, b2g-v2.1 affected, b2g-v2.2 affected)

RESOLVED WONTFIX
blocking-b2g -
Tracking Status
b2g-v2.0 --- affected
b2g-v2.1 --- affected
b2g-v2.2 --- affected

People

(Reporter: fmuyumba, Unassigned)

References

()

Details

(Whiteboard: [2.1-exploratory-3])

Attachments

(1 file)

Description: Creating or signing into a Firefox account, causes transition issues before the requested page is loaded Repro Steps: 1) Update a Flame device to BuildID: 20141120001207 2) launch "Settings" 3) Tap "Firefox Accounts" 4) Tap the "Create account or sign in" button 5) Observe what happens before the requested page is loaded Actual: Before the page is loaded, transition issues occur Expected: The requested page is loaded without transition issues Environmental Variables: Device: Flame 2.1 (319mb)(Kitkat Base)(Shallow Flash) BuildID: 20141120001207 Gaia: f8d3bf44029e0afc0124600a4bb34dba8fc1ad21 Gecko: f70a67a7f846 Version: 34.0 Firmware: V188-1 User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0 Repro frequency: 100% See attached: video clip & logcat: http://youtu.be/ZskJuFw3Mm8
Flags: needinfo?(dharris)
This issue repros on Flame 2.2 (319mb)(Kitkat Base)(Shallow Flash) and Flame 2.0 (319mb)(Kitkat Base)(Shallow Flash) Result: Before the requested page is loaded, transition issues occur Environmental Variables: Device: Flame 2.2 (319mb)(Kitkat Base)(Shallow Flash) BuildID: 20141120040205 Gaia: 1abe09b4925547699dfdb2d358aed019137c3aa6 Gecko: 6ce1b906c690 Version: 36.0a1 Firmware: V188-1 User Agent: Mozilla/5.0 (Mobile; rv:36.0) Gecko/36.0 Firefox/36.0 ------------------------------------------------------------------------------------------------------ Environmental Variables: Device: Flame 2.0 (319mb)(Kitkat Base)(Shallow Flash) BuildID: 20141120000206 Gaia: 1ede2666f1e6c1b3fd3b282011caf0cbc59544b0 Gecko: 54f1b0ee07a6 Version: 32.0 Firmware: V188-1 User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
QA Whiteboard: [QAnalyst-Triage?]
There are many similar flickering bugs in the settings app. This could be a possible dupe, but overall is minor. Not nominating to block
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(dharris)
Going to nominate this bug - the flash is pretty noticeable and rather jarring in the latest 2.2 build. Gaia e5d666d6f62480ced56c6d9352f5e12befb5a862 SourceStamp 5c4d07e2199e BuildID 20141124160209 Version 36.0a1 v188-1
blocking-b2g: --- → 2.2?
QA Contact: ddixon
This issue is not a regression as it happens on all branches.
If there's noticeable jank in the opening transition, this should be refiled under the window management component. FxA doesn't do anything special beyond opening a SystemDialog, it uses the default transitions.
NI to Peter, is it relevant to graphics? NI to Jenny, could you redirect to someone for comments on the visual?
Flags: needinfo?(pchang)
Flags: needinfo?(jelee)
ni Settings visual designer Helen on this. Thanks Helen =) Also ni Arthur to look into the possible cause of this issue, thanks Arthur!
Flags: needinfo?(jelee)
Flags: needinfo?(hhuang)
Flags: needinfo?(arthur.chen)
A page takes time to load, so maybe we should delay the play of the transition a little bit. Alive, any ideas?
Flags: needinfo?(arthur.chen) → needinfo?(alive)
I think this looks related to gaia changes, please let me know if needs graphic team's help.
Flags: needinfo?(pchang)
FxAccount is implemented in a standalone page which is loaded in an iframe inside system dialog; it does not wait for load before doing opening transition; IMO this is not a blocker because it is not a regression but enhancement/polish. I am c.c. Jared to let him know this.
Flags: needinfo?(alive) → needinfo?(6a68)
From visual perspective, I don't think the transition for the indicator is needed, and obviously it feels flickering when the page is loaded.
Flags: needinfo?(hhuang)
Flags: needinfo?(6a68)
triage: per comment 12, i think we should get this fixed. blocking.
blocking-b2g: 2.2? → 2.2+
(In reply to Wesley Huang [:wesley_huang] (EPM) (NI me) from comment #13) > triage: per comment 12, i think we should get this fixed. blocking. Does it match to any blocking criteria that we have now? https://wiki.mozilla.org/B2G/Triage#Issues_that_Should_Block
blocking-b2g: 2.2+ → 2.2?
(In reply to Kevin Hu [:khu] from comment #14) > (In reply to Wesley Huang [:wesley_huang] (EPM) (NI me) from comment #13) > > triage: per comment 12, i think we should get this fixed. blocking. > > Does it match to any blocking criteria that we have now? > https://wiki.mozilla.org/B2G/Triage#Issues_that_Should_Block I don't think we'd block the release for this, so clearing the nom.
blocking-b2g: 2.2? → -
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: