Bug 135862 - please don't use fixed width pages
Summary: please don't use fixed width pages
Alias: None
Product: Bugzilla
Classification: Community
Component: Bugzilla General   
(Show other bugs)
Version: 2.18
Hardware: All
OS: Linux
medium vote
Target Milestone: ---
Assignee: David Lawrence
QA Contact: David Lawrence
URL: http://www.uiwizards.com/wBloop23.html
Depends On:
TreeView+ depends on / blocked
Reported: 2004-10-15 15:04 UTC by Mike McLean
Modified: 2007-04-18 17:13 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-04-08 19:39:06 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Mike McLean 2004-10-15 15:04:02 UTC
Fixed width pages assume that all browsers are running about about the same
resolution with about the same font size, but this is not the case.

The current fixed width causes inconvenience when
  - users are using large fonts (perhaps for accessibility or because the user
is also using very high resolution).
  - users are using small browsers windows (perhaps because they just don't want
the browser to eat so much of their screen or because their screen resolution is

Comment 1 Mike McLean 2004-10-15 15:11:40 UTC
You can moderate one-half of the problem by using a font-size relative width
specification (em).  For example


This still leaves 800x600 browser windows in scrollbar territory.  I don't know
if there's a way solve that without dropping fixed-width entirely.

Comment 2 David Lawrence 2004-10-26 20:59:29 UTC
Ok set the use of min-width which I didnt know about. Does it look better now
when changing browser size?

Comment 3 Mike McLean 2004-10-26 22:15:57 UTC
It certainly helps on the large window end.  800x600 still has to scroll.

It might be better to specify min-width in a font-relative way (units: em or ex).

Comment 4 Mike McLean 2005-04-08 19:39:06 UTC

Note You need to log in before you can comment on or make changes to this bug.