Closed Bug 1242379 Opened 9 years ago Closed 8 years ago

Confirmation dialog does not work when choosing option “Ok”

Categories

(Firefox OS Graveyard :: Gaia::TV, defect, P3)

ARM
Gonk (Firefox OS)
defect

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: cbadescu, Unassigned)

References

Details

(Whiteboard: [ft:conndevices])

Steps to reproduce: 1.In “Dev Web Apps” navigate to “Youzeek” app and press “OK”(“Enter” key on the keyboard). 2.After detail page is loaded press “Back”(“Esc” key on the keyboard). 3.A confirmation dialog will display with “Cancel” and “Ok”, press “OK”(“Enter” key on the keyboard). Expected results: User should go back to “Dev Web Apps”. Actual results: User is still on “Youzeek” detail page. Note/Issues: I could reproduce this behaviour only when using this app. Are there any other apps that throw that confirmation dialog on exit, or is there a way we can create test apps for tv with this feature (apps that throw that pop-up on exit)? Environment: 2.5 Simulator. This issue is reproducing in -dev server. Video for this issue: https://www.dropbox.com/s/uqmu1rx8ryoe3r4/Youzeek-back.mp4?dl=0
please read "detail page" as "landing page"
No longer blocks: TV_Marketplace_2.5
Priority: -- → P1
Joseph, could you dig out what happened here?
Flags: needinfo?(jyeh)
It looks like the website itself has listened to the back key and pop up a confirm dialog. Visit the YOUZEEK website with browser (http://youzeek.com/helixdesktop.v4.aspx?device=fftv) and hit the backspace button also show up the same dialog.
Flags: needinfo?(jyeh)
It's a content issue. ni Michael to get attention.
Flags: needinfo?(mellis)
Joseph will update his further finding on which line seems wrong in the content.
In file https://youzeek.com/js/v4_Player-dev.js line 77: window.open("", "_self").close(); Did not close the window properly.
Blocks: 1243809
Issue confirmed on 2.1 TV. Thank you for reporting this issue, we will reach out to the partner for fix implementation. This bug is P3 and does not block release
Flags: needinfo?(mellis)
Priority: P1 → P3
@ David, can you please take a look here and provide a suggested fix for the partner?
Flags: needinfo?(dwalsh)
NI on Harald as David's backup during PTO
Flags: needinfo?(hkirschner)
Would we encourage such a pattern for partners? Facebook in your browser never asked if you really wanted to leave it. Sounds like something is wrong with the back button pattern when users accidentally exit out of apps.
Flags: needinfo?(hkirschner) → needinfo?(ehung)
Flags: needinfo?(dwalsh)
We don't support system-wise back button on 2.5, so if the content wants to deal with the back key by itself, it at least needs to take action (e.g. window.close()) when the user click "OK" on the dialog. However, on a real TV, if it calls window.close() to kill itself, the user will be taken back to TV app (i.e. broadcast TV), it's a customization made by TV vendor.
Flags: needinfo?(ehung)
Whiteboard: [ft:conndevices]
@David - mind investigating and providing a suggested solution for partner? Currently I have to press & hold the back arrow on remote to keep confirmation dialog box open. URL = http://youzeek.com/helixDesktop.v4.aspx?device=FFTV
Flags: needinfo?(dwalsh)
I agree with Harald -- we shouldn't encourage this, especially if it kicks out to broadcast TV. I would ask them to remove it.
Flags: needinfo?(dwalsh)
I did notice that if I'm in fullscreen video, and I tap "Return", the video doesn't go back to small size. That I would expect.
The "kicks out to live TV" should not weigh too much here, as Live Tv is the destination after leaving the app, regardless of whether or not the user is asked to confirm the decision. I am for the confirmation screen, (because user is likely to hit back arrow in experience without intending to exit) but if PE is in alignment that this is not preferred, then I must differ to their experience and expertise in this area.
Since web apps won't in 2.6 scope, this issue is not valid anymore after removing web apps from our build.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.