Closed Bug 980819 Opened 11 years ago Closed 10 years ago

[B2G][Email] The text and button has not align center in IMAP disable page

Categories

(Firefox OS Graveyard :: Gaia::E-Mail, defect, P3)

ARM
Gonk (Firefox OS)
defect

Tracking

(blocking-b2g:2.0+, b2g-v2.0 verified, b2g-v2.1 verified)

VERIFIED FIXED
2.0 S4 (20june)
blocking-b2g 2.0+
Tracking Status
b2g-v2.0 --- verified
b2g-v2.1 --- verified

People

(Reporter: edchen, Assigned: jrburke)

Details

Attachments

(4 files)

[Environment] Gaia 71f78f7f68fcf5e23cc5965fee0dad45289c438b Gecko https://hg.mozilla.org/mozilla-central/rev/5dc091b7e86f BuildID 20140304160205 Version 30.0a1 [Steps] 1. Launch email app and set a gmail account with Gmail. 2. Make sure that it can receive mails. 3. Go desktop of gmail setting to disable IMAP. 4. Close email app 5. Launch email app again, and then waiting for 1 min. 6. Show "IMAP Disable" page. [Actual result] The text as well as button has not center-text. [Expect result] The text as well as button has center-text.
QA Contact: edchen
Hardware: x86_64 → ARM
Summary: [Email] The text as well as button has not center-text. → [Email] The text and button has not align center in IMAP disable page
[Devices] Flame [Environment] Gaia 8d865839d932bfbd5e157f376f74d8cb12bfdd51 Gecko https://hg.mozilla.org/releases/mozilla-aurora/rev/1d4046a8cb6c BuildID 20140610000223 Version 32.0a2 ro.build.version.incremental=94 ro.build.date=Tue May 20 09:29:20 CST 2014
Summary: [Email] The text and button has not align center in IMAP disable page → [B2G][Email] The text and button has not align center in IMAP disable page
blocking-b2g: --- → 2.0?
blocking -- small visual issue with visual refresh
blocking-b2g: 2.0? → 2.0+
Attached file GitHub pull request
Some other error screens were also not up to date with the new visual design, so I also updated them: * gmail two-factor * bad password * imap/pop3 disabled I tested them by using these commands in the devtools console: require('api').onbadlogin(require('model').account, 'imap-disabled'); require('api').onbadlogin(require('model').account, 'bad-user-or-pass'); require('api').onbadlogin(require('model').account, 'needs-app-pass'); I will attach a screenshot of how they look now.
Assignee: nobody → jrburke
Status: NEW → ASSIGNED
Attachment #8441658 - Flags: review?(m)
Comment on attachment 8441658 [details] [review] GitHub pull request woo, thanks for the screenshots! r=mcav
Attachment #8441658 - Flags: review?(m) → review+
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
[Environment] Gaia 23e06c3624309db22ad9cb736d89700768b42b36 Gecko https://hg.mozilla.org/releases/mozilla-aurora/rev/12161a842a8e BuildID 20140618160200 Version 32.0a2 ro.build.version.incremental=94 ro.build.date=Tue May 20 09:29:20 CST 2014 [Result] Pass
Status: RESOLVED → VERIFIED
Attached video verify_video
This issue has been verified successfully on Flame v2.1 See attachment: verify_video.mp4 Reproducing rate: 0/5 Flame 2.1 versions: Gaia-Rev ccb49abe412c978a4045f0c75abff534372716c4 Gecko-Rev https://hg.mozilla.org/releases/mozilla-b2g34_v2_1/rev/18fb67530b22 Build-ID 20141130001203 Version 34.0 Device-Name flame FW-Release 4.4.2 FW-Incremental eng.cltbld.20141130.034738 FW-Date Sun Nov 30 03:47:49 EST 2014 Bootloader L1TC00011880
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: