Internet Explorer 11 specific error: "Relay frame could not be found " about django-browserid HOT 6 CLOSED

Thanks for the report!

This sounds like a Persona issue rather than a django-browserid issue, but that's not for certain.

I don't have a Windows machine handy to test on, and the IE testing VMs are taking forever for me to download for some reason, so I emailed [email protected] to ask if anyone else can help reproduce this problem.

Can you reproduce this issue on https://input.mozilla.org/? They're using the latest released version of django-browserid.

from django-browserid.

Unfortunately no, https://input.mozilla.org/ works fine for me using the same IE 11 setup, so I can't reproduce the issue there.

I should have mentioned that I'm testing django-browserid with http locally on my dev machine(s), whereas input.mozilla.org is using https of course.

My guess is that the combination of http (django-browserid) -> https (Persona popup window) reveals the (IE 11 only) issue?

Thanks for the quick response!

from django-browserid.

pyvideo uses http and also has an up-to-date django-browserid. You could test it there, too:

http://pyvideo.org/

from django-browserid.

I was able to get my hands on an IE11/Windows 8 setup to test on and can't replicate in on either input or pyvideo.

Some helpful people on the mailing list are pointing out that they get that error message when navigating directly to the sign-in page. @wiser1, are you getting the Persona sign-in page in a popup, or is it opening up in the same tab as your site? If it's the latter, it might indicate that somehow instead of calling navigator.id.request to trigger Persona login your site is navigating directly to the sign-in page.

from django-browserid.

@Osmose, I get the Persona sign-in page in a popup.

And, I've since found that I can only replicate the problem when the django-browserid app I'm testing has an IP address like 192.168.0.21. Everything works fine if I give the app a public IP address. I haven't found an easy workaround, so for now I'll just rarely test with IE, and will remember that no good deed goes unpunished by IE ;-). Not sure if it's worthwhile to investigate any further.

Thanks to all who responded and helped me get a handle on this!

from django-browserid.

Weeeeeiiiiiiiiiirrrrrrrrdddddd. I'm glad you were able to isolate it so well though.

I agree with the sentiment of "too obscure to worry about". Thanks for the report!

from django-browserid.