Bugzilla – Full Text Bug Listing
| Summary: | [client] [Opera] Login callout does not appear | ||
|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | Mark Macdonald <mamacdon> |
| Component: | Client | Assignee: | Project Inbox <orion.client-inbox> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | antonm, bokowski, john.arthorne, malgorzata.tomczyk, miket, pwebster, simon_kaegi, susan, Szymon.Brandys |
| Version: | 0.2 | ||
| Target Milestone: | 7.0 | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
|
Description
Mark Macdonald
Do we support Opera? I think that basic features like the Login Dialog should work, no matter we support Opera or not. I would say this is not a high priority for M5, but we should look at it during M6. I hope it is something trivial. Yes, me too. I'll get to it when I have time. Opera isn't currently in our plan, but we had a discussion on IRC yesterday with one of the Orion devs, and they are keen to help us in supporting Opera. At the very least it would be interesting to understand what the problems are so we can figure out if it is something we are doing wrong, or a bug in Opera. (In reply to comment #4) > with one of the Orion devs, and they are keen to help us in supporting Opera. with one of the _Opera_ developers :-) (In reply to comment #5) > (In reply to comment #4) > > with one of the Orion devs, and they are keen to help us in supporting Opera. > > with one of the _Opera_ developers :-) Could this Opera dev be added to CC here? If they want to help, I would like to know who should be added to other Opera related issues. Hello. :) Please feel free to cc me on any Opera related issues and I'll do my best to help out. Thanks. I can see that problem is a little different that I assumed. The problem lays not it displaying the login dialog itself, because if your select [Sign In] button (right top corner) the login dialog will display and you will be able to log in to Orion. Displaying the dialog immediately after page loads works because on first 401 error we call javascript function to open the dialog. After user sings it the call is renewed. Here the login page is not displayed and afterwards calls are not renewed. So I'll start looking for problems there. I found the cause of the problem (it was in fact just in front of our eyes). In auth.js#handleAuthenticationError we are using ioArgs.xhr.status to find out what exact problem with the response is. If it's 403 we display "Forbidden access" message, if it's 401 we pop up the login dialog. The problem is that on Opera returned ioArgs.xhr.status is 0. Somewhere I found information that Opera returns status=0 always when response error is between 300-499. So Mike, this is a question to you: can I get somehow the actual response error? At least know when it's 403 or 401? Unfortunately I failed to find it in google :( Hmm interesting. Let me do some digging. (In reply to comment #10) > Hmm interesting. Let me do some digging. ping (In reply to comment #11) > (In reply to comment #10) > > Hmm interesting. Let me do some digging. > > ping Good point. Mike did you look at it? Do we have any walkaround how to check if it's 401 or something else? > Mike did you look at it? Do we have any walkaround how to check if it's 401 or
> something else?
Yikes, long time to respond--sorry, have been traveling around the world (it seems). Is there a live URL to a recentish version online somewhere? There have been some fixes to various parts of XHR handling, so I'd like to check this out.
(In reply to comment #13) > > Mike did you look at it? Do we have any walkaround how to check if it's 401 or > > something else? > > Yikes, long time to respond--sorry, have been traveling around the world (it > seems). Is there a live URL to a recentish version online somewhere? There have > been some fixes to various parts of XHR handling, so I'd like to check this > out. I have created an account for you on our live beta server - http://orionhub.org. I sent you login details in a separate email. (In reply to comment #14) > (In reply to comment #13) > > > Mike did you look at it? Do we have any walkaround how to check if it's 401 or > > > something else? > > > > Yikes, long time to respond--sorry, have been traveling around the world (it > > seems). Is there a live URL to a recentish version online somewhere? There have > > been some fixes to various parts of XHR handling, so I'd like to check this > > out. > > I have created an account for you on our live beta server - > http://orionhub.org. I sent you login details in a separate email. Thanks, am able to log in without a problem using Opera Next/Mac (1040) and 11.11 stable. (In reply to comment #15) > Thanks, am able to log in without a problem using Opera Next/Mac (1040) and > 11.11 stable. I have Opera 11.11 build 2109 and while I can log in manually (click in the upper right corner), the expected behaviour is that a log in dialog appears automatically when you go to http://orionhub.org, or when you go directly to one of the pages under orionhub.org. So yes, I can log in (triggered manually), but the problem from comment 0 still happens, for example by going to http://orionhub.org/navigate/table.html#/file/ which shows the root of the navigator tree. (In reply to comment #16) > (In reply to comment #15) > > Thanks, am able to log in without a problem using Opera Next/Mac (1040) and > > 11.11 stable. > > I have Opera 11.11 build 2109 and while I can log in manually (click in the > upper > right corner), the expected behaviour is that a log in dialog appears > automatically when you go to http://orionhub.org, or when you go directly to > one of the pages under orionhub.org. > > So yes, I can log in (triggered manually), but the problem from comment 0 still > happens, for example by going to http://orionhub.org/navigate/table.html#/file/ > which shows the root of the navigator tree. Thanks Boris, I guess I just needed a refresher. Will dig in tomorrow. Mark, is it still an issue? (In reply to comment #18) > Mark, is it still an issue? The new login dialog has mostly fixed it, but there is still a problem here. Visiting the Navigator (or any page that requires authentication) never shows the "Authentication Required" callout. Sometimes the page will give an error or display "Loading..." forever. But you can ignore that and use the Security > Sign In menu to log in, after which everything works fine. (In reply to comment #19) > (In reply to comment #18) > > Mark, is it still an issue? > > The new login dialog has mostly fixed it, but there is still a problem here. > > Visiting the Navigator (or any page that requires authentication) never shows > the "Authentication Required" callout. Sometimes the page will give an error or > display "Loading..." forever. > > But you can ignore that and use the Security > Sign In menu to log in, after > which everything works fine. I'd say until we fix our XHR bugs that prevent the callout from appearing, this is a good enough resolution to the original problem. (In reply to comment #19) > (In reply to comment #18) > > Mark, is it still an issue? > > The new login dialog has mostly fixed it, but there is still a problem here. > > Visiting the Navigator (or any page that requires authentication) never shows > the "Authentication Required" callout. Sometimes the page will give an error or > display "Loading..." forever. > > But you can ignore that and use the Security > Sign In menu to log in, after > which everything works fine. The other problem is that we can't tell that it's 401 that prevented the data to load. So after user loggs in using the scenario you described calls are not renewed. To get all the data loaded user has to reload the page. (In reply to comment #21) > (In reply to comment #19) > > (In reply to comment #18) > > > Mark, is it still an issue? > > > > The new login dialog has mostly fixed it, but there is still a problem here. > > > > Visiting the Navigator (or any page that requires authentication) never shows > > the "Authentication Required" callout. Sometimes the page will give an error or > > display "Loading..." forever. > > > > But you can ignore that and use the Security > Sign In menu to log in, after > > which everything works fine. > > The other problem is that we can't tell that it's 401 that prevented the data > to load. So after user loggs in using the scenario you described calls are not > renewed. To get all the data loaded user has to reload the page. We've recently fixed a ton of XHR bugs and implemented most of the XHR2 spec. I'm not certain exactly when it will be in a public release--but it's a good sign. As soon as I get my hands on a mac build I'll test things out. :) The problem was described in comment 9, so Mike you can verify if it was one of the problems addressed recently. This bug is currently not our biggest problem on Opera. I downloaded the latest version today and see what I found: Bug 364798. Just commented on the bug--for future reference, test with http://www.opera.com/browser/next/ to check for any fixes in the pipeline. Thanks! Opera is not supported by Orion. This is a very old bug, closing. Old, unsupported browser and won't fix. |