couldn't find an existing [open] bug on this, so...
i've tried the following command-line options, all of which do nothing to change
the size of the browser window (which maintains the same size from its previous
mozilla -height 200
mozilla -width 200
mozilla -height 200 -width 200
am using today's 2000.08.24.08 opt bits on Win98. i don't have access to the
linux bits today --timeless, pavlov or jrgm, could you see whether these options
work at all on linux? my guess is that they won't, but ya never know.
so, like if these commands aren't supposed to work as i've issued 'em, pls let
me know if
1. they ain't implemented. then we should either implement 'em, or pull 'em out.
2. i'm somehow issuing the commands incorrectly. strange, but lemme know the
correct way. thx!
with gramps on sabbatical, who should be the lucky owner of this bug?
Solaris8Intel build from tuesday's tip doesn't seem to use these params either.
Nav triage team: [nsbeta3-], leaving assigned to Don for the time being.
methinks the fix to this might be dependent on fixes for bug 20573...
Since Don has left, Vishy is taking his bugs in bulk, pending reassignment.
Netscape Nav triage team: this is not a Netscape beta stopper.
Could this be implemented anytime soon? The company I work for is planning to
use mozilla & XUL under Linux for our core borwser component, and it would be
very desirable to have geometry ability from the command line.
Marking nsbeta1- bugs as future to get off the radar.
Since this does not seem to get resolved soon, could someone please change the
accordingly, i.e. deleted the lines involving -height and -width? (And on that
occasion rename Win32 in the Unix/Linux section to Unix/Linux?)
Or should I open a new bug for this?
It's interesting to note that in Debian, the -width and -height arguments
work in the 1.0.0 package and in the 1.5-3 package, but not in the 1.6-5
This bug applies to latest 1.7.6 on WinXP and Linux GTK2+XFT trunk as well.
Note that the following:
mozilla -P profilename -height 768 -width 1024 -browser http://www.google.com
will bring up a Google window 1024px wide and 768px high, but it will be
chromeless in which no keyboard functions for controls, such as ctrl++, ctrl+- &
ctrl+h, do anything at all.
*** Bug 238607 has been marked as a duplicate of this bug. ***
fwiw, a hack to force mozilla to have a specifc geometry
(via a mozilla/init.d pluggable shell script) can be find
*** Bug 323128 has been marked as a duplicate of this bug. ***
This bug exists in the Firefox/184.108.40.206 (OpenSuSE Linux):
Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-GB; rv:220.127.116.11) Gecko/20060527 SUSE/18.104.22.168-1.3 Firefox/22.214.171.124
My tests show that MOST commandline options are ignored, -width, -height, -ProfileManager, -P <profile>. This occurs when calling firefix and also when calling firefox-bin directly.
When firefox exits, the following content gets written to localstore.rdf :
(I hope I copied the correct portion out of the file!)
This is irrespective of the current window geometry.
Hope this helps,
This is, at least in part, related to Bugzilla Bug 317903. There it is explained that profile commandline options are ignored unless the environment variable MOZ_NO_REMOTE is set to 1 (tcsh: "setenv MOZ_NO_REMOTE 1", bash: "export MOZ_NO_REMOTE=1"). This might also affect other commandline options.
Setting MOZ_NO_REMOTE to 1 has helped in my case to display and enable profiles.
Personally, I think that a warning message should appear to explain that commandline options were ignored and what to do so that they are not!
*** Bug 352328 has been marked as a duplicate of this bug. ***
*** Bug 364729 has been marked as a duplicate of this bug. ***
*** Bug 388419 has been marked as a duplicate of this bug. ***
MOZ_NO_REMOTE=1 has no effect
MOZ_NO_REMOTE=1 firefox -height 500 -width 400
has no effect.
I confirm that:
firefox -height 800 -width 600
...has not effect.
Build identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:126.96.36.199) Gecko/2008072820 Firefox/3.0.1
per bug 444319, turning this into a seamonkey bug.
suggest combining with #20573 per discussion there.
Has this been fixed? It's working for me now, but is undocumented as far as I can tell, and doesn't show up in "firefox --help." So is it working by accident or by design?
I can confirm that it is working in Mozilla Firefox 4.0b6 and that it does not show up in the -help output. This is on a 32-bit Linux system.
Yeah they aren't shown anywhere anymore, so no reason to believe they would work either.
Whops, indeed they are working. Just not documented.