On Fri, Nov 13, 2009 at 1:17 AM, Mark Wubben <m...@novemberborn.net> wrote: > Wouldn't this depend on whether the response contains HTTP Auth headers? > It'd be very odd if an OAuth request caused a dialog to appear. In fact, > especially when handling OAuth requests getting the 401 response is the only > way of knowing whether the access credentials are invalid.
Hi Mark :) I was only talking about the case where an auth challenge is served and the browser would typically present a username/password dialog. This is the situation I thought TOP was in, because it was all I could reproduce with the sample code. In this case, when XHR is started from a Chrome extension view (like a background page or popup), Chrome will drop the request on the floor and never respond. The bug is that the extension view doesn't know how to create the auth dialog so it does nothing there. Is there also an issue when the auth dialog is *not* expected to occur? - a -- You received this message because you are subscribed to the Google Groups "Chromium-extensions" group. To post to this group, send email to chromium-extensi...@googlegroups.com. To unsubscribe from this group, send email to chromium-extensions+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/chromium-extensions?hl=.
