Better understand/document browser compatibility #1212

minrk opened this Issue Dec 28, 2011 · 8 comments


None yet
4 participants

minrk commented Dec 28, 2011

The notebook is known to work well with current Chrome and Firefox. Safari and apparently Opera appear to work reasonably well, but it seems that Safari doesn't work with secure (wss) connections, and the same may be true of Opera. This may be a certificate issue, and the same thing may be affecting Opera. Once we better understand the causes of these issues, notes should be added to docs.

This SO question may be relevant for the Safari wss issue.


takluyver commented Jan 1, 2012

Referring to this tornado issue, is it the case that Chrome 16 has broken the websockets again?


minrk commented Jan 1, 2012

No, I don't believe so. 16 is the same version that we saw issues with before, it just became the stable release last week, so a new crop of users started seeing it.


minrk commented Jan 1, 2012

I should also note that we monkeypatch tornado 2.1/2.1.1 with the related fix, so it shouldn't affect IPython users.


takluyver commented Jan 2, 2012

Ah, ok, I'd forgotten about the monkeypatch.


ellisonbg commented Apr 12, 2012

What specifically needs to happen to resolve this issue?


minrk commented Apr 28, 2012

To close this issue, we need docs that cover various known-good and known-bad version combinations, e.g.

Bad: Safari + wss + untrusted certificate
Bad: Safari + IPython 0.12 + tornado ≥ 2.2.0
Bad: Opera (at all, I think)
Good: Safari + IPython ≥ 0.12.1 + tornado ≥ 2.1.0

I can't recall any bad version/case failures for reasonably current Chrome or Firefox, but we should confirm that current Chrome and FF work in both http and https cases with both minimum (2.1.0) and current dev tornado.


minrk commented Jan 19, 2013

I started a notebook compatibility page, closing here.

minrk closed this Jan 19, 2013

minrk added this to the no action milestone Mar 26, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment