Last Comment Bug 908925 - linkedin shows a blank page
: linkedin shows a blank page
Status: RESOLVED DUPLICATE of bug 826348
[serversniff] [sitewait]
:
Product: Tech Evangelism
Classification: Other
Component: Mobile (show other bugs)
: Trunk
: Other Gonk (Firefox OS)
: -- critical (vote)
: ---
Assigned To: Nobody; OK to take it and work on it
:
Mentors:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-08-23 16:38 PDT by Michelle Luna
Modified: 2014-01-28 03:41 PST (History)
10 users (show)
See Also:
Crash Signature:
(edit)
QA Whiteboard:
Iteration: ---
Points: ---


Attachments
adb logcat of reloading blank linkedin screen (141.53 KB, text/plain)
2013-08-23 16:38 PDT, Michelle Luna
no flags Details
b2g_browser_linkedIn.png (15.89 KB, image/png)
2013-09-13 17:01 PDT, Tony Chung [:tchung]
no flags Details

Description Michelle Luna 2013-08-23 16:38:34 PDT
Created attachment 794936 [details]
adb logcat of reloading blank linkedin screen

On ZTE Open

1. go to browser
2. go to linkedin.com and login
3. blank screen appears (you can scroll around a bit, but can't ever get to the site, it is just a blank grey screen

I have one report of this in the English support forum and I can repro on my ZTE Open device.
Comment 1 (Inactive after June) George Duan [:gduan] [:喬智] 2013-08-25 09:47:36 PDT
I tested on chrome and firefox browser on my phone and found out, after login, the page stay in a grey screen. The reason is |https://touch.www.linkedin.com| use wrong uri for their script files, so their pages is not initialized well (tested on my chrome with mobile user-agent).

It's probably linkedin's own problem.
Comment 2 Naoki Hirata :nhirata (please use needinfo instead of cc) 2013-09-13 03:16:51 PDT
Michelle, which version of firefox OS are you using?
Comment 3 Michelle Luna 2013-09-13 16:09:43 PDT
Hi Naoki,

This is on the commercial build of ZTE Open for Spain. Today, on my v1.0.1 ZTE Open from Spain and my v1.0.1 Alcatel from Colombia I can see the Linkedin login screen, but the Login button does nothing (I can reproduce this on v1.1 on geeksphone keon also). I see the same problem on Firefox for Android:

1. go to linkedin.com
2. enter login credentials
3. a Loading dialog appears for a split second, but I'm not logged into the site (stuck at login page)

I expected to be logged into the site. 

Stock Android browser works fine, so maybe this is evangelism?
Comment 4 Roland Tanglao :rolandtanglao 2013-09-13 16:27:20 PDT
IMHO it's evangelism aka website compatibility because linkedin works if you follow these
Steps:
0. Open Firefox for Android 23, Android 4.3, Nexus 4
1. Check the "Request Desktop Site" box in the Firefox for 23 Android Menu
2. goto http://linkedin.com and then do a refresh


What do you see?
1. We receive the desktop content of linkedin and it works on Firefox for Android
2. On Firefox OS you see a brief Javscript popup displaying "loading" and then white screen
3. On Firefox for Android with "Request Desktop Site" unchecked you see brief Javscript popup displaying "loading" and then white screen
4. On the stock Android browser for Android 4.3, Chrome, with "Request desktop site" it works after refreshing linkedin.com just like FF for Android; like FF for Android the mobile site doesn't work nor does the touch site.

What do you expect?
On firefox os and android, the mobile content of linkedin.


What is the version of the browser?
1. Firefox for Android 23
2. Firefox OS 1.0.1 bundled browser based on Gecko 18
Comment 5 Naoki Hirata :nhirata (please use needinfo instead of cc) 2013-09-13 16:57:19 PDT
What seems odd is Michelle had stated stock android works fine; I tried change the UA string in Firefox Browser and I still see the issue in the desktop browser after changing the UA to a Nexus UA string...

It might be that I am tired and seeing things.  :|
Comment 6 Tony Chung [:tchung] 2013-09-13 17:01:14 PDT
Created attachment 804790 [details]
b2g_browser_linkedIn.png

Yeah this is certainly a TE bug.   i tried logging in myself, and am faced with a white page and a message at the top:

{statusCode":500"message":"{[TypeError: Cannot read property 'appVersion' of undefenied]\n caught: true, \n coreThrown: false,\n catchable: true,\n rethrown: true}"}

Screenshot attached.

My environment:
- Buri 1.2 nighty build, buildID 20130912040201
- User agent: Mozilla/5.0 (Mobile; rv:26.0) Gecko/26.0 Firefox 26.0

STR: launch browser App, goto linkedin.com (redirects to touch site), and login with credentials.
Comment 7 Tony Chung [:tchung] 2013-09-13 17:06:57 PDT
oh wait, is this a dupe of bug 826348?
Comment 8 Roland Tanglao :rolandtanglao 2013-09-13 17:20:35 PDT
(In reply to Tony Chung [:tchung] from comment #7)
> oh wait, is this a dupe of bug 826348?

yeah it looks like a dupe of bug 826348! hopefully the server change in https://bugzilla.mozilla.org/show_bug.cgi?id=826348#c12 will fix both ffos and firefox for android

p.s. i think michelle was using stock android browser in an older version of Android NOT Chrome in Android 4.3 (in Android 4.3 there is no stock android browser IIRC)
Comment 9 Jason Smith [:jsmith] 2013-09-13 20:59:58 PDT

*** This bug has been marked as a duplicate of bug 826348 ***
Comment 10 Karl Dubost :karlcow 2013-09-15 15:55:48 PDT
I do not think it is a duplicate. bug 826348 is about linkedin serving the desktop version instead of the mobile version. Here it seems to be an issue with JS and/or JS. This is different.
Comment 11 Adrian Crespo 2014-01-28 03:41:41 PST
It is not a duplicate. When a user loads the mobile version, there is an error:
http://pastebin.com/trvS7n4x

ERROR:
touch.www.linkedin.com : server does not support RFC 5746, see CVE-2009-3555

CVE-2009-3555 is a server side vulnerability which might allow to compromise a TLS/SSL session and may be preventing to load the Linkedin mobile website.

Related docs:
https://wiki.mozilla.org/Security:Renegotiation#Action
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-3555
http://stackoverflow.com/questions/3575233/how-to-by-pass-following-error-in-firefox-extension-server-does-not-support-rfc

Note You need to log in before you can comment on or make changes to this bug.