Closed Bug 20391 Opened 20 years ago Closed 19 years ago

Window size should depend on screen_resolution


(SeaMonkey :: Preferences, defect, P3)



(Not tracked)



(Reporter: rzach, Assigned: mcafee)



(Keywords: polish)


(1 file)

The window size of the prefs dialog (as well as lots of other dimensions
throughout Mozilla) should be calculated from the broswer.screen_resolution
preference.  In Linux, when you set that pref to 120 or 140, the window is too
small to display the dialog correctly.

Build 1999.11.30.08 Linux.
Assignee: shuang → german
there a couple of other related issues to pref window sizes. reassign it to
german for decision on size, and platform.
Assignee: german → don
Target Milestone: M14
I am not even sure hwo we can tackle this from the perspective of CSS using
screen res, but in theory using absolute measures for CSS font sizes like 3.5mm
should give you this for free? does this work properly in Gecko? re-assigning to
Don to see what can in theory be done about this. Past dogfood!
Target Milestone: M14 → M15
Past beta too.
i just wrote some expermental js functions to size the browser based on the js
screen object and am calling it from the Startup() function.

One thing i noticed was that in order for these functions to work, i had to
explicitly remove the width="640" height="480" from my <window tag in the xul

otherwise, it prevents any dynamic initial sizing of the loading browser window.
it bacicly locks down the size so you can't change it at all.
(I am on unix.)
I even tried to resize from calling setAttribute().
nochange until i removed the width and height.

I thought i would point this out.

Bulk move of all Pref UI component bugs to new Preferences component.  Pref UI 
component will be deleted.
Component: Pref UI → Preferences
Move to M16 for now ...
Target Milestone: M15 → M16
Target Milestone: M16 → M18
Move to M21 target milestone.
Target Milestone: M18 → M21
this is a stale bug. it has not been touched in more 30 no longer
reperducible and i suggest it be marked WFM.
On my machine, the symptoms of this bug haven't changed.
Since Don has left, Vishy is taking his bugs in bulk, pending reassignment.
Assignee: don → vishy
*** Bug 69150 has been marked as a duplicate of this bug. ***
Assignee: vishy → mcafee
QA Contact: cpratt → sairuh
This bug also exists elsewhere in the DB (I know I reported it at least once). 
Nominating for mozilla 1.0 - this looks very unprofessional, and prefs is
usually one of the first things someone sees of a new browser.  Also, I think
this is OS All; I think I saw something similar on Win32

From the bug recently marked as a dup:

When you load a brand-new installation of the browser and hit Preferences,
the dialog box pops up far too small for all the UI elements.  They get
cut off at the right and bottom.  And the box has no resize handles.

You can resize it if your window manager has a forcible resize command, and
it then remembers the size it was set to, but this will be extremely
confusing and irritating to new users (who may have no idea that there is
any such thing as a forcible resize).

I suspect this is a general problem with XPToolkit dialog boxes; the "open
file" dialog box comes up with the right hand side of the list cut off, too. 
They should take their size from the size of the elements they contain.

Keywords: mozilla1.0, polish
OS: Linux → All
I have also run into this problem on Win 98 (First Edition), Mozilla Build
I set my message box text (using the Display Control Panel) to use the Georgia
font at 11 point size prior to installing Mozilla.  My resolution is 1024x768. 
When I went to the Preferences-Font screen, I found the Set Resolution area to
be truncated, similar to what is shown in the initial bug report. 
*** Bug 80535 has been marked as a duplicate of this bug. ***
bug 21810 was marked fixed today. Doesn't that also fix this one?
ben fixed the pref window to respect font size
back in mid-may sometime.  marking fixed, over
to him if we need to reopen.
Closed: 19 years ago
Resolution: --- → FIXED
okay, vrfy.
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.