Full Screen Layout and excessive line width

RESOLVED INVALID

Status

SeaMonkey
General
--
enhancement
RESOLVED INVALID
16 years ago
14 years ago

People

(Reporter: Giovanni Pelosi, Assigned: asa)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

16 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2a) Gecko/20020910
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2a) Gecko/20020910

I found that full screen mode (F11) is quite unusable without sidebar (F9).

I like this mode of browsing, but when i switch to full screen,
i got very large line width and text line that "wraps",
depending on font size ctrl+/ctrl-,
at a large number of char.

the "optimal" line size for reading is 60 to 70 char
so i must adjust sidebar width to correct wrapping.

i cannot do this in Phoeneix, for instance.

OK, screen width/height is not good for screen reading (as a book)
but a better handling of screen width in full-screen mode
i think is possible

an adjustable draggable margin ?
a  width sizeable window ?

an optimal layout for onscreen reading,
imho, could be this one:

an optional true full-screen,
(hidable navigation toolbar)

with a vertical and sizeable tab-bar on the left

(similar to opera)

in this way

+--------+----------------------------------------------------------------+
|---------+
|---------+
|---------+
|  Tab
|  Bar
|
| Sizeable
|  left/right
|
|      <= | =>
|
+--------------------------------------------------------------------------+



releted to Bug 126746

Reproducible: Always

Steps to Reproduce:
1.
2.
3.

Actual Results:  
wrapping of lines too wide for good reading

Expected Results:  
the user should be able to adjust width
to read optimal 60/70 char wrapping

Comment 1

16 years ago
just edit [mozilla install directory]/res/*.css

perhaps
body { max-width: 65em; }
Status: UNCONFIRMED → RESOLVED
Last Resolved: 16 years ago
Resolution: --- → INVALID
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.