Closed
Bug 1143817
Opened 10 years ago
Closed 7 years ago
[Clock][Alarm] Alarm scroll position will carry over to multiple separate alarms.
Categories
(Firefox OS Graveyard :: Gaia::Clock, defect)
Tracking
(tracking-b2g:backlog, b2g-v2.0 affected, b2g-v2.1 affected, b2g-v2.2 affected, b2g-master affected)
RESOLVED
WONTFIX
tracking-b2g | backlog |
People
(Reporter: Marty, Unassigned)
References
()
Details
(Whiteboard: [3.0-Daily-Testing])
Attachments
(1 file)
34.73 KB,
text/plain
|
Details |
Description:
If the user is viewing Alarm 1, and scrolls all the way to the bottom, then switches to view Alarm 2, that alarm will also be scrolled to the bottom. This also applies to creating new alarms, possibly leading to the user not seeing the Alarm Name text field. This scroll position will also persist after deleting the last alarm.
Repro Steps:
1) Update a Flame to 20150316010202
2) Launch the Clock app.
3) Create 2 different alarms
4) View the first alarm, and scroll to the bottom
5) Go back and then view the second alarm, note the scroll position.
6) Go back again and select the New Alarm icon, note the scroll position.
Actual:
The scroll position persists across multiple alarms, even when making a new alarm.
Expected:
Scroll position starts at the top the first time each alarm is independently viewed
Environmental Variables:
Device: Flame 3.0 (319MB)(Full Flash)
Build ID: 20150316010202
Gaia: 4868c56c0a3b7a1e51d55b24457e44a7709ea1ae
Gecko: 436686833af0
Gonk: b83fc73de7b64594cd74b33e498bf08332b5d87b
Version: 39.0a1 (3.0)
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:39.0) Gecko/39.0 Firefox/39.0
Repro frequency: 5/5
See attached: video (URL), logcat
Reporter | ||
Comment 1•10 years ago
|
||
This issue DOES occur on Flame 2.2, 2.1, and 2.0 builds.
The scroll position persists across multiple alarms, even when making a new alarm.
Environmental Variables:
Device: Flame 2.2 (319MB)(Full Flash)
Build ID: 20150316002502
Gaia: a6b2d3f8478ec250beb49950fecbb8a16465ff6f
Gecko: 18619f8f6c5c
Gonk: b83fc73de7b64594cd74b33e498bf08332b5d87b
Version: 37.0 (2.2)
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0
Environmental Variables:
Device: Flame 2.1 (319MB)(Full Flash)
Build ID: 20150316001204
Gaia: 90f4ca618048b608c8e663d3e1d84781cfa719a8
Gecko: 65e67896e813
Gonk: b83fc73de7b64594cd74b33e498bf08332b5d87b
Version: 34.0 (2.1)
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0
Environmental Variables:
Device: Flame 2.0 (319MB)(Full Flash)
Build ID: 20150316000201
Gaia: 896803174633fc6acd3fd105f81c349b8e9b9633
Gecko: 2fc0c40fd074
Gonk: b83fc73de7b64594cd74b33e498bf08332b5d87b
Version: 32.0 (2.0)
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(pbylenga)
Comment 2•10 years ago
|
||
NI on component owner for nomination decision and assignment
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(pbylenga) → needinfo?(twen)
Comment 3•10 years ago
|
||
Not blocking bug, set tracking flag.
tracking-b2g:
--- → ?
Flags: needinfo?(twen)
Comment 4•9 years ago
|
||
Hello, I am interested in taking this up as my first bug.I was able to make relevant changes
I would like to know how to run the packaged app from my local gaia repository on a simulator post making changes to the js files.please help.I am currently getting only a blank screen.The default apps in the simulator run perfectly fine.
Comment 5•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
•