80404 - category items don't fit

Status: RESOLVED DUPLICATE of bug 539738

(SeaMonkey :: Preferences, defect)

Description

[sairuh (rarely reading bugmail)]

the category items are too wide to fit in the now narrower category tree region.
ben suggested reducing the indent to fix this.

Comment 1

[sairuh (rarely reading bugmail)]

Attachment: shot of classic on linux [19:08 build]

Comment 2

[sairuh (rarely reading bugmail)]

Attachment: shot of modern on linux [19:08 build], pretty similar to classic

Comment 3

[sairuh (rarely reading bugmail)]

Attachment: more recent linux build shot [classic, 21:28 pull]

Comment 4

[sairuh (rarely reading bugmail)]

Attachment: more recent linux build shot [modern, 21:28 pull]

Comment 5

[sairuh (rarely reading bugmail)]

this is more exacerbated on mac. going to attach screenshots from 2001.05.17.08 
comm verif build...

Comment 6

[sairuh (rarely reading bugmail)]

Attachment: mac modern, shot #1

Comment 7

[sairuh (rarely reading bugmail)]

Attachment: mac modern, shot #2

Comment 8

[sairuh (rarely reading bugmail)]

Attachment: mac classic, shot #1

Comment 9

[sairuh (rarely reading bugmail)]

Attachment: mac classic, shot #2

Comment 10

[timeless]

sarah: your modern fonts for buttons/labels is using smallcaps, do you have a 
bug or explanation for that?

Comment 11

[sairuh (rarely reading bugmail)]

timeless: heh, yeah. i had set my mac appearance settings [from the control
panel] to use a small caps style.

i'll go and set 'em back to a, uh, more default-like setting, and retake those
screenshots. :) my hunch is that it might not make a diff, but ya never know!

Comment 12

[sairuh (rarely reading bugmail)]

i changed my large system font from Capitals to Charcoal [i cannot remember if 
Charcoal is the default one there], and the prefs panel looked the same [except 
for the dialog titlebar].

however, i did note that if the scrollbar is visible, the category items are even 
shorter. will attach screenshots. 

Comment 13

[sairuh (rarely reading bugmail)]

Attachment: more abbreviated - modern, replaces part #2

Comment 14

[sairuh (rarely reading bugmail)]

Attachment: more abbreviated - classic, replaces part #2

Comment 15

[Viswanath Ramachandran]

nav triage: moving to p3, mozilla0.9.3. 

Comment 16

[Frank Tang]

just a reminder that german translation may need 150% of English space to fit 
the string. make sure your fix also work for German translation. 

Comment 17

[sairuh (rarely reading bugmail)]

see bug 87195, where "Offline and Disk Space" is now the widest item in the
category tree.

Comment 18

[jglick]

Not much of a help in the grand scheme of this bug I realize, but we could use 
"&" instead of "and".

And "Mail and Newsgroups" could be "Mail & News"?

Comment 19

[sairuh (rarely reading bugmail)]

i'd be very happy if "Mail and Newgroups" changed to "Mail & News" --is there
perchance an existing bug on either changing the "and" or shortening to "News"?

Comment 20

[scottputterman]

I don't know of any, but "Mail & News" works for me, too.

Comment 21

[Paul Chen]

nav triage team:

Pushing out to mozilla1.0, in the interim, we're going to make the pref window
resizeable and default window size localizeable. Long term, this issues need to
be ironed out.

Comment 22

[Ben Goodger (use ben at mozilla dot org for email)]

.9.8 for investigation

Comment 23

[sairuh (rarely reading bugmail)]

*** Bug 116184 has been marked as a duplicate of this bug. ***

Comment 24

[sairuh (rarely reading bugmail)]

with the outliner landing, i've noticed that more category names appear
abbreviated. unsure if this would have anything to do with bug 118154, where the
column picker is now present...

Comment 25

[sairuh (rarely reading bugmail)]

Attachment: shot of classic [linux 01.04 build]

Comment 26

[sairuh (rarely reading bugmail)]

Attachment: shot of modern [linux 01.04 build]

Comment 27

[andreww]

perhaps we should add a splitter widget  to prefs - ala sidebar in nav :)

Comment 28

[Jan Varga [:janv]]

Attachment: without column picker

Comment 29

[jglick]

Is there any reason Prefs needs the selector widget visible? 

Comment 30

[Joe Hewitt (gone)]

Can we just hide the column headers altogether and just go back to the old way,
with a label above the outliner?

Comment 31

[Michael Lefevre]

*** Bug 145613 has been marked as a duplicate of this bug. ***

Comment 32

[R. D. Flowers]

Still showing targetted for 1.1alpha -- LONG gone !

Comment 33

[chris hofmann]

too late for 1.6. let's try for 1.7.

Comment 34

[R. D. Flowers]

This bug creates a shoddy appearance to anyone who encounters it (which is not
that hard or rare). I literally can't see why anyone would consider leaving the
display static like this. It is almost as if little terminals, unknowably long
strings (i18n) etc. etc. did not exist.

Or does this bug have tenure by now?

Comment 35

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 36

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 37

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 38

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 39

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 40

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 41

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 42

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420

Comment 43

[Karsten Düsterloh]

Duping against where the action will happen, eventually.