In builds up to at least M13, specifying a -chrome command line option would open the URL specified in that option as a chrome window, instead of the normal window. This is no longer the case Steps to Reproduce: These steps are described assuming the win32 command line: 1. Start mozilla with "mozilla.exe -chrome chrome://bookmarks/content" - Actual Results The normal Mozilla browser window opens. - Expected Results The bookmarks window should have opened. Tested in build 2000020919

Added zopestudio keyword.

Possible workaround: Create a HTML file that contains JavaScript along the lines of: window.open(ChromeURL, WindowName, 'chrome'); window.close(); where ChromeURL is the URL of the chrome you wish to open, WindowName a string to name the opened window. Now use this file on the mozilla command line. This is an untested workaround, and an ugly hack.

Todays build has fixed this. My apologies for the wasteing of your bandwith and time.

I take it noone will mind that I now close this one. =)

What a pain I must be. That'll teach me. Right: On Windows98, -chrome command line does not work after component.reg has been created. Tested on 2000021108. To reproduce: 1. Take clean mozilla build, in an empty directory 2. Start mozilla with "mozilla.exe -chrome chrome://bookmarks/content" 3. Close the resulting bookmarks window 4. Start mozilla again, same command line as step 2. 5. Close resulting browser window 6. Delete component.reg 7. Again start mozilla, same command line, see step 2. - Actual Results: At step 2 the bookmarks window opens. At step 4, the regular browser window opens. And at step 7, the bookmarks window opens again. - Expected Results: The bookmarks window should have opened on all three accounts.

this is a duplicate of bug #27800 that I also logged last night.

damn. before yesterday, -chrome was working (it worked on the 2-13-00 build). but it broke last night, see 27800

sspitzer, do you know who should own this bug? dveditz, same as 27800? or do you want to resolve this one as a duplicate? right now, no one is looking at this.

This works for me on NT with 2/21 build. I ran mozilla with -chrome it loaded up the new chrome package just fine.

reassigning browser-general bugs (again!) so triagers can find all the bugs with one query.

mj@digicool.com: can you retry this with a recent build? the bug of which sspitzer thought was a duplicate has been resolve.d

OK, works again in latest build (2000022108). Marked WORKSFORME. Thanks for the trouble, guys. Good luck with the crunch!

Verified working with 3/7 win32 bits under NT and 98