Closed
Bug 1017294
Opened 11 years ago
Closed 11 years ago
8x25_v1.3_FFOS : Music Fast forward and rewind is not happening when performed long tap on Music Widget in device locked state and from notification tray.
Categories
(Firefox OS Graveyard :: Gaia::Music, defect)
Tracking
(tracking-b2g:backlog, b2g-v2.0 affected, b2g-v2.0M affected, b2g-v2.1 affected, b2g-v2.2 fixed)
RESOLVED
FIXED
| tracking-b2g | backlog |
People
(Reporter: lcelebi, Unassigned)
Details
(Whiteboard: [caf priority: p3][CR 665600][perf-reviewed])
Attachments
(2 files)
8x25_v1.3_FFOS : Music Fast forward and rewind is not happening when performed long tap on Music Widget in device locked state and from notification tray.
preconditions:
Some music files are present in device.
Steps:
1. Play a music from music player.
2. Short press power key to lock the device.
3. Music Player widget is displayed in home screen after device lock.
4. Long tap on Next button to fast forward the music.
5. Long tap on Previous button to rewind the music playback and observe.
6. Also try to fast forward and rewind by long tapping on the button from Music widget present in notificatioon tray.
Actual Result:
Music Fast forward and rewind is not happening when performed long tap on Music Widget in device locked state and from notification tray.
Comment 1•11 years ago
|
||
NI'ing Jacqueline to confirm if this is a bug or works as designed.
Flags: needinfo?(jsavory)
Comment 2•11 years ago
|
||
In triage today it came up as feature request. We will not be fixing in 1.3 and hence backlog.
blocking-b2g: 1.3? → backlog
Comment 3•11 years ago
|
||
Yes, the user should be able to fast forward and rewind on the lock screen and notification tray as they do on the music app.
Flags: needinfo?(jsavory)
Updated•11 years ago
|
Whiteboard: [CR 665600] → [caf priority: p3][CR 665600]
Updated•11 years ago
|
Whiteboard: [caf priority: p3][CR 665600] → [caf priority: p3][CR 665600][perf-reviewed]
Comment 4•11 years ago
|
||
Hi Dominic,
As offline discussion, prev/next buttons are not able to receive contextmenu events, I've put WIP patch on github, could you take a look and give me some feedback? thanks.
Attachment #8482045 -
Flags: feedback?(dkuo)
Comment 5•11 years ago
|
||
Comment on attachment 8482045 [details] [review]
WIP
Sherman, the approach looks pretty straightforward and good to me, I don't know why the playback widget couldn't receive the contextmenu event either, it's probably because system app has its own behavior, maybe we can needinfo the system peers? and feel free to ping me again if you have addressed the issues and need the review, thanks!
Attachment #8482045 -
Flags: feedback?(dkuo) → feedback+
Comment 6•11 years ago
|
||
Hi Alive,
Do you have any idea that contextmenu event is not received on playback widget button?
I've done some test, contextmenu event can be received on div element, but not no button element.
Flags: needinfo?(alive)
Comment 7•11 years ago
|
||
(In reply to Sherman Chen [:chens] from comment #6)
> Hi Alive,
>
> Do you have any idea that contextmenu event is not received on playback
> widget button?
> I've done some test, contextmenu event can be received on div element, but
> not no button element.
No idea. Platform issue maybe.
Flags: needinfo?(alive)
Comment 8•11 years ago
|
||
Attachment #8501644 -
Flags: review?(dkuo)
Attachment #8501644 -
Flags: feedback?(alive)
Comment 9•11 years ago
|
||
Comment on attachment 8501644 [details] [review]
Pull request
I'll let Dominic review this part.
Also flag Greg for lockscreen change.
Attachment #8501644 -
Flags: feedback?(alive) → feedback?(gweng)
Comment 10•11 years ago
|
||
Comment on attachment 8501644 [details] [review]
Pull request
I think we should avoid nested switching case. This is really confused. And, should we create test for media playback widget? Since it's growing and I don't find any unit test (at least I found nothing).
Attachment #8501644 -
Flags: feedback?(gweng)
Comment 11•11 years ago
|
||
Comment on attachment 8501644 [details] [review]
Pull request
Thanks Greg, I've update PR and addressed the comments, would you take a look and give some feedback?
Attachment #8501644 -
Flags: feedback?(gweng)
Comment 12•11 years ago
|
||
Hi Dominic, I have some updates in the PR, could you review the patch? Thanks!
Flags: needinfo?(dkuo)
Comment 13•11 years ago
|
||
Comment on attachment 8501644 [details] [review]
Pull request
feedback+ with one nit.
Attachment #8501644 -
Flags: feedback?(gweng) → feedback+
Comment 14•11 years ago
|
||
Comment on attachment 8501644 [details] [review]
Pull request
Sherman, the patch looks okay but I found an major issue which might break the fast-seeking function so let's tweak this patch and I will review it again after you address the issues, please read the github comments, thanks!
Flags: needinfo?(dkuo)
Attachment #8501644 -
Flags: review?(dkuo)
Comment 15•11 years ago
|
||
Comment on attachment 8501644 [details] [review]
Pull request
Hi Dominic, I've updated PR and comments addressed, could you review again?
Thanks!
Attachment #8501644 -
Flags: review?(dkuo)
Comment 16•11 years ago
|
||
Comment on attachment 8501644 [details] [review]
Pull request
Sherman, thanks for addressing those issues and now the patch looks good to me! though there is one possible improvement that, the media_playback.js under system and lockscreen seems exactly the same, so could we merge them into one then put it in the shared/ folder? if so, it can be a followup and please file one bug and let's do it :)
Attachment #8501644 -
Flags: review?(dkuo) → review+
Comment 17•11 years ago
|
||
Gaia-try: https://treeherder.mozilla.org/ui/#/jobs?repo=gaia-try&revision=a89a39cb39c8
Master: https://github.com/mozilla-b2g/gaia/commit/d5465ee468db890002ba4560c10503da0821c1de
Thanks Domi :)
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
status-b2g-v2.0:
--- → affected
status-b2g-v2.0M:
--- → affected
status-b2g-v2.1:
--- → affected
status-b2g-v2.2:
--- → fixed
| Assignee | ||
Updated•10 years ago
|
blocking-b2g: backlog → ---
tracking-b2g:
--- → backlog
You need to log in
before you can comment on or make changes to this bug.
Description
•