Closed
Bug 1063054
Opened 11 years ago
Closed 7 years ago
[Calendar][New Event] Start Date field can become off-centered within selection box upon changing.
Categories
(Firefox OS Graveyard :: Gaia::Calendar, defect)
Tracking
(b2g-v2.0 affected, b2g-v2.1 affected, b2g-v2.2 affected)
RESOLVED
WONTFIX
People
(Reporter: onelson, Unassigned)
References
Details
Attachments
(2 files)
Description:
When the user changes the value of the start date for a new event in 'Calendar', may experience the text becoming off-centered and hugging the top-left corner. Issue appeared most likely to occur after creating a name and When field for the event, along with the first time this application was run after a fresh restart.
Repro Steps:
1) Update a Flame device to BuildID: 20140904000203
2) Open 'Calendar' app.
3) Create new event with '+' icon in top right.
4) *Set name, When fields.
5) Set Start Day field.
6) Observe position of text in field.
Actual:
Start Day field is updated but now off-centered and placed in top-left corner.
Expected:
Start Day field is updated. Remains centered.
Environmental Variables:
Device: Flame 2.1 (319mb)
BuildID: 20140904000203
Gaia: a47ecb6368c015dd72148acde26413fd90ba3136
Gecko: 757931d0149e
Version: 34.0a2 (2.1)
Firmware: V123
User Agent: Mozilla/5.0 (Mobile; rv:33.0) Gecko/33.0 Firefox/33.0
Repro frequency: 10/20 (50%; seems to lower if user reloads the the application; occurs most often on first run of application from fresh boot)
See attached:
logcat
screenshot_calendarUI_startDateOffCentered.png
Reporter | ||
Comment 1•11 years ago
|
||
Reporter | ||
Comment 2•11 years ago
|
||
Issue REPROES in flame 2.2 (512mb), flame 2.0:
Field Start Date in Calendar when creating New Event becomes off-centered when manipulated.
===========================================================================================
Environmental Variables:
Device: Flame Master (512mb)
Build ID: 20140904040204
Gaia: 008026e932b64b4a70b9931c3da96986583bc8d4
Gecko: 776fa9cf70cd
Version: 35.0a1 (Master)
Firmware Version: v123
User Agent: Mozilla/5.0 (Mobile; rv:35.0) Gecko/35.0 Firefox/35.0
Environmental Variables:
Device: Flame 2.0 (319mb)
BuildID: 20140904000202
Gaia: d056733f8a7a1a152f5458b323f092c47dbffa48
Gecko: 19383abee78a
Version: 32.0 (2.0)
Firmware: V123
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(pbylenga)
Comment 3•11 years ago
|
||
QAWanted for branch checks to see if this is a regression.
Updated•11 years ago
|
QA Contact: ckreinbring
Updated•11 years ago
|
QA Contact: ckreinbring → croesch
Comment 4•11 years ago
|
||
This bug repro's on Flame KK builds: Flame 2.2, Flame 2.1, Flame 2.0, Flame 2.0 Base, OpenC 2.2
Revised STR:
1. Launch Calendar
2. Tap on New Event (+)
3. Tap on a text field and rapidly tap lettters then quickly tap on the date/time wheel while the letters being typed are trying to catch up.
4. Tap OK and there's a good chance the date/time will now be offset in the selection box.
***NOTE: This bug will most likely take several tries to get.
Repro Rate: 10/20
Environmental Variables:
Device: Flame Master KK
BuildID: 20140919052449
Gaia: d170091ba1b5597b05f37fb259f6b8eb02568798
Gecko: 3475e6a1665a
Version: 35.0a1 (Master)
Firmware Version: L1TC10011800
User Agent: Mozilla/5.0 (Mobile; rv:35.0) Gecko/35.0 Firefox/35.0
-----------------------------------------------------------------
Environmental Variables:
Device: Flame 2.1 KK
BuildID: 20140919050548
Gaia: f0f22bb46c881e02524b3991c2587ff8c0a9fc37
Gecko: ab2a88c05a4b
Version: 34.0a2
Firmware Version: L1TC10011800
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0
-----------------------------------------------------------------
Environmental Variables:
Device: Flame 2.0 KK
BuildID: 20140919041249
Gaia: 31434a3949556171f3565ca47ac2b44e810e95e6
Gecko: fb1589259e4f
Version: 32.0 (2.0)
Firmware Version: L1TC10011800
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
-----------------------------------------------------------------
Device: Flame 2.0 KK Base
BuildID: 20140904160718
Gaia: 506da297098326c671523707caae6eaba7e718da
Gecko:
Version: 32.0 (2.0)
Firmware: V180
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
-----------------------------------------------------------------
Device: Open_C 2.2
BuildID: 20140919052449
Gaia: d170091ba1b5597b05f37fb259f6b8eb02568798
Gecko: 3475e6a1665a
Version: 35.0a1 (2.2)
Firmware: P821A10v1.0.0B06_LOG_DL
User Agent: Mozilla/5.0 (Mobile; rv:35.0) Gecko/35.0 Firefox/35.0
Updated•11 years ago
|
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(jmitchell)
Comment 6•11 years ago
|
||
Hi Oliver,
Sorry, I could not reproduce this.
Could you kindly provide a video for reproducing?
Thanks.
Flags: needinfo?(onelson)
Comment 7•11 years ago
|
||
I've been trying to reproduce this bug and out of about 75 tries I've only got it to happen Once! This bug seems very hard to get now. I wasn't able to get video of it when it did happen. This bug used to be a lot easier to get.
Repro: 1/75
Comment 8•11 years ago
|
||
Video Link: http://youtu.be/pyZ1uXiYGLg
Finally was able to get this bug on video. It may look confusing but it's just following the steps in comment 4 in the build below. In this build it's not too hard to get this bug.
My previous comment 7 was on the latest 2.2 and 2.1 KK builds and was super hard to get.
Environmental Variables:
Device: Flame 2.1
BuildID: 20140904062538
Gaia: a47ecb6368c015dd72148acde26413fd90ba3136
Gecko: ffb144a500a4
Version: 34.0a2 (2.1)
Firmware Version: v188
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage?]
Flags: needinfo?(onelson) → needinfo?(jmitchell)
Updated•11 years ago
|
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(jmitchell)
Comment 9•11 years ago
|
||
Hi Cody,
Thanks for the video.
I can reproduce this now.
Comment 11•7 years ago
|
||
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•