Closed
Bug 1217242
Opened 10 years ago
Closed 7 years ago
[FM-Radio] User will not expect tapping the star next to a favorited station to unfavorite/remove that station.
Categories
(Firefox OS Graveyard :: Gaia::FMRadio, defect)
Tracking
(b2g-v2.2 affected, b2g-master affected)
RESOLVED
WONTFIX
People
(Reporter: Marty, Unassigned)
References
()
Details
(Whiteboard: [2.5-Daily-Testing][Spark][priority] 2.6UXnom)
Attachments
(1 file)
|
81.10 KB,
text/plain
|
Details |
Description:
If the user has a favorited stations, and they tap the yellow star next to the favorited station, that station will be removed from the station list. There isn't any indication that tapping on the star will remove the favorited station.
The user may tap this, expecting the radio to tune to that station, or may just be tapping the station list item, happen to incidentally tap the star, and be confused why it disappeared instead of tuning (this is what happened to me.)
Note: This refers specifically to the stars next to each frequency listing in the Favorite Station list, and not the Favorite/Unfavorite star in the top right of the app. The video URL demonstrates this.
Repro Steps:
1) Update a Flame to 20151021064220
2) Plug in a pair of headphones and launch the FM Radio app
3) Tune to 99.9 MHz, and star that station
4) Tap the star next to the 99.9 MHz listing in the Favorite Stations area
Actual:
The 99.9 MHz favorite station will be removed from favorites.
Expected:
The Radio app will tune to the 99.9 MHz station.
Environmental Variables:
Device: Flame 2.5 319MB
Build ID: 20151021064220
Gaia: 32d827a70af90a05918f234e5b16b35d5d2a07e8
Gecko: 473aefe5bd85842eeb142e0cde8e2cd21edbf40b
Gonk: c4779d6da0f85894b1f78f0351b43f2949e8decd
Version: 44.0a1 (2.5)
Firmware Version: v18D
User Agent: Mozilla/5.0 (Mobile; rv:44.0) Gecko/44.0 Firefox/44.0
Repro frequency: 10/10
See attached: Video (URL), Logcat
| Reporter | ||
Comment 1•10 years ago
|
||
This issue DOES occur on Flame 2.2 builds.
The 99.9 MHz favorite station will be removed from favorites.
Environmental Variables:
Device: Flame 2.2 319MB
BuildID: 20151021032506
Gaia: 885647d92208fb67574ced44004ab2f29d23cb45
Gecko: d546c2eb1c0c
Gonk: bd9cb3af2a0354577a6903917bc826489050b40d
Version: 37.0 (2.2)
Firmware Version: v18D
User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0
******************************
FM Radio is not included in Spark Aries builds.
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
Comment 2•10 years ago
|
||
No-Jun, is this by design? I think the reporter believes this could be confusing to the end user because tapping anywhere else around that favorite station changes it to that station.
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker) → needinfo?(npark)
Comment 3•10 years ago
|
||
I believe this is by design, since this behavior was from the beginning. Perhaps there is a UX rationale behind it, pinging :tif for more info.
Flags: needinfo?(npark) → needinfo?(tshakespeare)
Comment 4•10 years ago
|
||
Chiming in for Tif here
I agree that this behaviour is unclear. Temporarily, I think we should remove this function and just let the user remove the radio station through the star button at the top.
Right now its unclear that tapping the star will remove your favourites and its a bit destructive in the sense that you can easily accidentally remove your stations.
Flags: needinfo?(tshakespeare)
Comment 5•10 years ago
|
||
Good candidate for increasing the quality of the release. noming for 2.6
blocking-b2g: --- → 2.6?
Comment 6•10 years ago
|
||
Hub,
Ni'ing you to keep this in your radar for fix.
Thanks
hema
Flags: needinfo?(hub)
Whiteboard: [2.5-Daily-Testing][Spark] → [2.5-Daily-Testing][Spark][priority]
Updated•10 years ago
|
blocking-b2g: 2.6? → ---
Updated•10 years ago
|
Whiteboard: [2.5-Daily-Testing][Spark][priority] → [2.5-Daily-Testing][Spark][priority] 2.6UXnom
Updated•9 years ago
|
Flags: needinfo?(hub)
Comment 7•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
•