If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

[Calendar] The warning for a suspicious login attempt is cut off not fully visible

NEW
Unassigned

Status

Firefox OS
Gaia::Calendar
3 years ago
3 years ago

People

(Reporter: rpribble, Unassigned)

Tracking

unspecified
ARM
Gonk (Firefox OS)

Firefox Tracking Flags

(b2g-v2.2 affected)

Details

(Whiteboard: [2.2-Daily-Testing])

Attachments

(2 attachments)

(Reporter)

Description

3 years ago
Created attachment 8511241 [details]
Screenshot.png

Description:
The error message warning the user of a suspicious login attempt on their account as seen when signing in to the calendar is cut off and not entirely visible.

Prerequisites:
1) Trigger a 'suspicious login attempt' warning on your email account (try changing device location, switching to data, etc.)

Repro Steps:
1) Update a Flame device to BuildID: 20141024040202
2) Enter calendar
3) Drawer icon > settings > add an account
4) Enter login information and sign in
6) On the following confirmation page, observe red warning at the top of the screen
  
Actual:
The warning message for a suspicious sign in attempt is cut off.
  
Expected: 
Warning message is easily visible and accessible to user.
  
Environmental Variables:
Device: Flame 2.2 Master KK (319 MB)
BuildID: 20141024040202 (full flash)
Gaia: d893a9b971a0f3ee48e5a57dca516837d92cf52b
Gecko: a5ee2769eb27
Gonk: 05aa7b98d3f891b334031dc710d48d0d6b82ec1d
Version: 36.0a1 (2.2 Master)
Firmware: V188
User Agent: Mozilla/5.0 (Mobile; rv:36.0) Gecko/36.0 Firefox/36.0
  
Repro frequency: 5/5
See attached: Screenshot, logcat
(Reporter)

Comment 1

3 years ago
Created attachment 8511242 [details]
Logcat.txt
(Reporter)

Updated

3 years ago
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(pbylenga)
Minor UI bug on a potential edge case, doesn't inhibit functionality or the purpose the error provides.
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(pbylenga)
You need to log in before you can comment on or make changes to this bug.