Closed
Bug 1246913
Opened 9 years ago
Closed 9 years ago
Focus does not move correctly for action message in Youzeek
Categories
(Firefox OS Graveyard :: Gaia::TV, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: cbadescu, Unassigned)
References
Details
(Whiteboard: [ft:conndevices])
Attachments
(1 file)
1.05 MB,
image/png
|
Details |
Steps to reproduce:
1.Launch the simulator and navigate to “Dev Web Apps”.
2.In “Dev Web Apps” navigate to “Youzeek” app and press “OK”(“Enter” key on the keyboard).
3.Navigate to a video and press “OK”.
Expected results:
Video start to play.
Actual results:
Two action buttons are displayed and a message under the buttons with a check-box. Navigating to right the focus moves from action button “Don’t allow” to the check-box.
Note/Issues:
Also the action buttons are displayed over the information text and the check-box.
Environment: 2.5 Simulator.
This issue is reproducing in -dev server.
Video to this issue: https://www.dropbox.com/s/525kl0iufpttc1x/Launch-first-time.mp4?dl=0
Comment 1•9 years ago
|
||
That's due to the resolution is not Full HD 1920x1080, please help to verify again with the supported resolution(greater than 1920x1080)
Flags: needinfo?(mlien)
Comment 2•9 years ago
|
||
This is the correct resolution shown
Are you sure that "Navigating to right the focus moves from action button “Don’t allow” to the check-box" is due to resolution issue?
Updated•9 years ago
|
Whiteboard: [ft:conndevices]
Comment 4•9 years ago
|
||
I am unable to confirm this bug on the 2.1 TV. Although, I do not recall encountering this issue on the Device during first launch.
@Mike - Does YouZeek launch and play for you well on the 2.5 TV?
Flags: needinfo?(mlien)
Comment 5•9 years ago
|
||
I can launch and play YouZeek on 2.5 TV normally and never encounter the focus issue on my simulator environment
Flags: needinfo?(mlien)
Comment 6•9 years ago
|
||
Thanks Mike & Cosmin. Closing this bug as Invalid
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•