1011386 - [Midori][3rd-party app][Entanglement] Entanglement show white screen after click “get the music” “play on mobile” options

Status: RESOLVED FIXED

(Firefox OS Graveyard :: Gaia::System::Window Mgmt, defect, P2)

Description

[sync-1]

DEFECT DESCRIPTION:
 [3rd APK][Entanglement]Entanglement freeze after click “get the music”“play on mobile” options
 
  REPRODUCING PROCEDURES:
 1.Access Entanglement
 2.Open menu->GET MORE
 3.Click “get the music” or “play on mobile” options->Entanglement freeze，click screen no response.--->KO1
 4.Long press homekey->Entanglement appear white screen--->KO2
 
  EXPECTED BEHAVIOUR:
 KO1：No freeze
 KO2：No white screen
 
  ASSOCIATE SPECIFICATION:
 
  TEST PLAN REFERENCE:
 
  TOOLS AND PLATFORMS USED:
 
  USER IMPACT:serious
 
  REPRODUCING RATE:3/3
 
  For FT PR, Please list reference mobile's behavior:
 Beetle_lite_FF(V18J+FP)：OK.
 
 CONTACT INFO (Name,Phone number):
 张番,[phone]-8755

Comment 1

[sync-1]

Attachment: jrdlog-PR677533

Comment 2

[Lingling Zhao]

Hi Vance,

Can you notice the developer to fix it? Thanks.

Comment 3

[Vance Chen [:vchen][skype:vance.lucida][[e-mail]]]

Hi Derek -

Do you have any update on this issue?

Thanks

Comment 4

[Derek Detweiler]

Hi Vance,

These links call "window.open(url)". I just checked https://developer.mozilla.org/en-US/Apps/Build/API_support_table and it appears that Entanglement isn't "certified" and wouldn't have this permission? Is there an analogous method I should use or do all outgoing links need to be removed?

Comment 5

[Lingling Zhao]

@ [e-mail],

Can you answer the questions in Comment4 please?
Thanks.

Comment 6

[Vance Chen [:vchen][skype:vance.lucida][[e-mail]]]

Hi Howie -

Could you find someone in the system frontend team to answer the question in Comment#4 ? thanks!

Comment 7

[howie [:howie]]

Hi Tim, can you help on Comment 4 , thanks.

Comment 8

[Tim Guan-tin Chien [:timdream] (please needinfo)]

A) I don't know how we come up with the conclusion that the app is using |window.open| here.
B) |window.open| should work everywhere. What won't work everywhere is to push the opened frame to another process (as the table suggests).
C) Reading the STR I cannot figure out what happened.

(In reply to Vance Chen [:vchen][[e-mail]] from comment #6)
> Could you find someone in the system frontend team to answer the question in
> Comment#4 ? thanks!

Your colleagues in Taipei are named "System Platform" team, for the purpose of "functional team" organization in FxOS.

Comment 9

[Vance Chen [:vchen][skype:vance.lucida][[e-mail]]]

(In reply to Tim Guan-tin Chien [:timdream] (MoCo-TPE) (please ni?) from comment #8)
> A) I don't know how we come up with the conclusion that the app is using
> |window.open| here.

The conclusion is drew from Comment#4, the author of the app mentioned that he use window.open(url) to open the url


> B) |window.open| should work everywhere. What won't work everywhere is to
> push the opened frame to another process (as the table suggests).
> C) Reading the STR I cannot figure out what happened.
> 

Basically it is just that in the step 3 of the STR, the app will try to visit a link via the function call window.open(url). However, he found that it is denied. The app author checked https://developer.mozilla.org/en-US/Apps/Build/API_support_table and it appears that Entanglement isn't "certified" so he wonder maybe that the reason it won't works?


> (In reply to Vance Chen [:vchen][[e-mail]] from comment #6)
> > Could you find someone in the system frontend team to answer the question in
> > Comment#4 ? thanks!
> 
> Your colleagues in Taipei are named "System Platform" team, for the purpose
> of "functional team" organization in FxOS.

Sorry, my bad, since you guys are all experts to everything about frontend, I always tend to think you guys are system frontend team. Again, my bad, and Howie already correct me on that.

Comment 10

[Tim Guan-tin Chien [:timdream] (please needinfo)]

(In reply to Vance Chen [:vchen][[e-mail]] from comment #9)
> (In reply to Tim Guan-tin Chien [:timdream] (MoCo-TPE) (please ni?) from
> comment #8)
> > A) I don't know how we come up with the conclusion that the app is using
> > |window.open| here.
> 
> The conclusion is drew from Comment#4, the author of the app mentioned that
> he use window.open(url) to open the url
> 
> 

OK.


> > B) |window.open| should work everywhere. What won't work everywhere is to
> > push the opened frame to another process (as the table suggests).
> > C) Reading the STR I cannot figure out what happened.
> > 
> 
> Basically it is just that in the step 3 of the STR, the app will try to
> visit a link via the function call window.open(url). However, he found that
> it is denied. The app author checked
> https://developer.mozilla.org/en-US/Apps/Build/API_support_table and it
> appears that Entanglement isn't "certified" so he wonder maybe that the
> reason it won't works?

No. |window.open| should always work.

Can we get a video on this bug? I wonder what had failed.

Comment 11

[Vance Chen [:vchen][skype:vance.lucida][[e-mail]]]

(In reply to Tim Guan-tin Chien [:timdream] (MoCo-TPE) (please ni?) from comment #10)
> (In reply to Vance Chen [:vchen][[e-mail]] from comment #9)
> > (In reply to Tim Guan-tin Chien [:timdream] (MoCo-TPE) (please ni?) from
> > comment #8)
> > > A) I don't know how we come up with the conclusion that the app is using
> > > |window.open| here.
> > 
> > The conclusion is drew from Comment#4, the author of the app mentioned that
> > he use window.open(url) to open the url
> > 
> > 
> 
> OK.
> 
> 
> > > B) |window.open| should work everywhere. What won't work everywhere is to
> > > push the opened frame to another process (as the table suggests).
> > > C) Reading the STR I cannot figure out what happened.
> > > 
> > 
> > Basically it is just that in the step 3 of the STR, the app will try to
> > visit a link via the function call window.open(url). However, he found that
> > it is denied. The app author checked
> > https://developer.mozilla.org/en-US/Apps/Build/API_support_table and it
> > appears that Entanglement isn't "certified" so he wonder maybe that the
> > reason it won't works?
> 
> No. |window.open| should always work.
> 
> Can we get a video on this bug? I wonder what had failed.

After testing the Entanglement couple times, I find that white screen problem is due to network access denied. And the reason for the network access denied is probably due to the tester test this issue in China.

Hi Lingling, per discussion, please have your QA team to test again this issue with some foreign carriers SIM card

And Derek, you might want to modify the error handle mechanism in your app such that if the |open.window(url)| is fail due to some network errors, the screen will show something else instead of just a whitescreen.

Thanks!

Comment 12

[Lingling Zhao]

Dears,

We test it again with T-Mobile card in China, after click “get the music” option, it goes to the right url.  The other little question is the screen freeze for 5s before the url displayed, maybe it is also because of the network. 

Thanks for all your strong support!

Comment 13

[Derek Detweiler]

> And Derek, you might want to modify the error handle mechanism in your app such that if the
> |open.window(url)| is fail due to some network errors, the screen will show something else
> instead of just a whitescreen.

I'm honestly not sure how to handle this. Those links are all cross-domain, so I believe all I would receive on this end is a window object with properties I cannot access (regardless of whether the link failed or succeeded). I'm not aware of a way to have the game determine whether the link failed.

Comment 14

[Chris Kreinbring [:CKreinbring]]

Bug partially repros on Flame 2.1 and Buri 2.1

Flame 2.1
Build ID: 20140702040207
Gaia: 85e97290431ce6aa0a965421e84d6070cd899129
Gecko: 7075808c3306
Platform Version: 33.0a1
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:33.0) Gecko/33.0 Firefox/33.0

Buri 2.1
Build ID: 20140702060700
Gaia: b0ddb2122771e25cdd880359406a53b10cdc0507
Gecko: e82a9700f94b
Platform Version: 33.0a1
Firmware Version: v1.2device.cfg
User Agent: Mozilla/5.0 (Mobile; rv:33.0) Gecko/33.0 Firefox/33.0

Actual result:  After selecting "Get the music" or "Play on Mobile" from the Get More menu the resulting page loads correctly.  However, long-pressing the Home button causes the Entanglement card to show as a blank rectangle, but it shows properly after being moved in either direction.

Comment 15

[Michael Ellis]

"Get Music" is no longer an option from the menu.  App now has "Get Maps" as the only "get" option from the main menu.

Closing this bug