288041 - no HTTP auth dialog when loading chrome url from command line

Status: RESOLVED EXPIRED

(Firefox :: General, defect)

Description

[Doug Holland]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041217
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

In the process of developing a custom application using XUL and Javascript, I
discovered that when I load up my application from the command line using the
--chrome chrome://myapp/content/ option, the browser element in my application
should bring up an HTTP Auth dialog so I can enter a username and password, then
let me login normally to my web site.  Unfortunately, there is no auth dialog,
it just brings up my browser widget with an Authorization Required error.  This
only happens when I load up my custom chrome from the command line.  If I bring
up the same chrome from Firefox's address bar, it works fine.  I've discovered
that this bug manifests in Firefox versions 1.0.1 and 1.0.2, but not in Firefox
1.0.0 - my app works fine there.

Reproducible: Always

Steps to Reproduce:
1. Set up a simple web site, use Apache or whatever web server you use to
require HTTP Auth with a username and password to access this site
2. Set up a simple XUL application with a browser element with the src attribute
pointing to above web site.
3. Try invoking the XUL application both by typing in the chrome URI in
Firefox's address bar, and by invoking firefox from the command line with the
--chrome option to bring up the application

Actual Results:  
When bringing up the website from the command line ("./firefox --chrome
chrome://myapp/content/", no HTTP Auth dialog comes up requesting a username and
password, just gets an error message in place of the web site saying
"Authorization Required."  Same behavior manifests foe me in Windows and Linux.

Expected Results:  
When bringing up the web site from the command line with the --chrome option, it
should bring up an HTTP Auth dialog asking for username and password, then
should bring up the website correctly in the browser element (assuming correct
username and password.)

Bug appears in Firefox versions 1.0.1 and 1.0.2, but not 1.0.0.  It manifested
for me both in Linux and in Windows 2000.

Comment 1

[:Gavin Sharp [email: [e-mail]]]

Possibly a regression from bug 277574.

Can you try this with the following builds and post the results? Use either
Linux or windows, whichever you prefer. These are the builds from before and
after that bug's patch went in (on the 17th).

Windows:
http://archive.mozilla.org/pub/firefox/nightly/2005-02-16-06-aviary1.0.1/ 
http://archive.mozilla.org/pub/firefox/nightly/2005-02-18-06-aviary1.0.1/

Linux:
http://archive.mozilla.org/pub/firefox/nightly/2005-02-16-07-aviary1.0.1/
http://archive.mozilla.org/pub/firefox/nightly/2005-02-18-07-aviary1.0.1/

Comment 2

[Doug Holland]

Interesting...  I tried both builds you suggested (the Linux builds that is...)
and both of them caused this bug to manifest.  Maybe this is not the regression
you thought it was... :p

Comment 3

[:Gavin Sharp [email: [e-mail]]]

If this really is a regression on the 1.0.1 branch, then it should be fairly
easy to find. Starting with
http://archive.mozilla.org/pub/firefox/nightly/2005-02-03-15-aviary1.0.1/ , can
you try working through the aviary1.0.1 builds in that directory to see when the
regression happened? Try the first build, then try one in the middle, etc until
you can narrow down the range.

Your help in tracking this down would be greatly appreciated.

Comment 4

[Doug Holland]

I just tried
http://archive.mozilla.org/pub/firefox/nightly/2005-02-04-07-aviary1.0.1/ - the
earliest Linux build of aviary1.0.1 AFAICT, and that version still has the
problem.  Weird.

Comment 5

[:Gavin Sharp [email: [e-mail]]]

And you're sure that it works as it should in the 1.0 release?

Comment 6

[Doug Holland]

Yep, tested it multiple times, under both Windows and Linux - works correctly 
when I use Firefox 1.0.0, but not with 1.0.1 or 1.0.2.  If I have time, I'll 
see if I could put together a test case, but I have other fires to fight for 
the time being... 
 
Thanks for the help. 
 

Comment 7

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 8

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.