LinkedIn.com profiles sometimes do not render correctly

Bug #1355703 reported by Brendan Donegan on 2014-08-12
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Oxide
Undecided
Unassigned

Bug Description

I'm not sure yet exactly what combination of layout causes this rendering bug, but at least for my profile page - and for some other profile pages which I have seen, but won't post screengrabs of as I don't have the skill to redact the personal information without losing the important details, the rendering of the top of the page is all wrong. A picture speaks a thousand words so please see the attached screenshot and picture, comparing Chrome on Android to Oxide on Ubuntu Touch.

summary: - LinkedIn.com profiles sometimes to not render correctly
+ LinkedIn.com profiles sometimes do not render correctly
Chris Coulson (chrisccoulson) wrote :

Olivier, do you think this might be a UA string sniffing issue?

It looks like it also isn't showing any images

Olivier Tilloy (osomon) wrote :

Brendan, I’m not observing the issue. I’m attaching a screenshot of what your linkedin page looks like on my device.

Can you advise on how to reproduce?

Olivier Tilloy (osomon) wrote :

Ah, I’m seeing a little warning icon over the padlock one in the android screenshot, could it be that linkedin is trying to load insecure content over a secure connection?

Brendan, can you attach the following log file, just after reproducing the issue?

    /home/phablet/.cache/upstart/application-legacy-webbrowser-app-.log

Yep, lots of messages like this:

qml: [JS] (https://touch.www.linkedin.com/?sessionid=4097821657530368&or=true&rs=false&ahoy=no#you:0) [blocked] The page at 'https://touch.www.linkedin.com/?sessionid=4097821657530368&or=true&rs=false&ahoy=no#you' was loaded over HTTPS, but displayed insecure content from 'http://m.c.lnkd.licdn.com/media/p/4/005/059/157/0cc282c.jpg': this content should also be loaded over HTTPS.

Olivier Tilloy (osomon) wrote :
Chris Coulson (chrisccoulson) wrote :

I tested this with https://code.launchpad.net/~chrisccoulson/oxide/ssl-status-api - the content now displays correctly, but the API indicates a degraded security level as expected. The actual bug is a Linkedin bug (somebody should probably report it to them)

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers