Closed Bug 80404 Opened 22 years ago Closed 13 years ago

category items don't fit

Categories

(SeaMonkey :: Preferences, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 539738

People

(Reporter: bugzilla, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [ben-radar])

Attachments

(11 files, 2 obsolete files)

the category items are too wide to fit in the now narrower category tree region.
ben suggested reducing the indent to fix this.
Blocks: 80392
Keywords: nsbeta1, ui
this is more exacerbated on mac. going to attach screenshots from 2001.05.17.08 
comm verif build...
Attached image mac modern, shot #1
Attached image mac modern, shot #2 (obsolete) —
Attached image mac classic, shot #1
Attached image mac classic, shot #2 (obsolete) —
sarah: your modern fonts for buttons/labels is using smallcaps, do you have a 
bug or explanation for that?
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!
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. 
Keywords: nsbeta1nsbeta1+
Priority: -- → P2
Target Milestone: --- → mozilla0.9.2
Whiteboard: [ben-radar]
nav triage: moving to p3, mozilla0.9.3. 
Priority: P2 → P3
Target Milestone: mozilla0.9.2 → mozilla0.9.3
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. 
Depends on: 87195
see bug 87195, where "Offline and Disk Space" is now the widest item in the
category tree.
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"?
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"?
I don't know of any, but "Mail & News" works for me, too.
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.
Target Milestone: mozilla0.9.3 → mozilla1.0
.9.8 for investigation
Status: NEW → ASSIGNED
Target Milestone: mozilla1.0 → mozilla0.9.8
*** Bug 116184 has been marked as a duplicate of this bug. ***
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...
Attachment #35086 - Attachment is obsolete: true
Attachment #35088 - Attachment is obsolete: true
perhaps we should add a splitter widget  to prefs - ala sidebar in nav :)
Attached image without column picker
Is there any reason Prefs needs the selector widget visible? 
Can we just hide the column headers altogether and just go back to the old way,
with a label above the outliner?
Target Milestone: mozilla0.9.8 → mozilla0.9.9
Target Milestone: mozilla0.9.9 → mozilla1.1
*** Bug 145613 has been marked as a duplicate of this bug. ***
Blocks: prefsfit
No longer blocks: 80392
Still showing targetted for 1.1alpha -- LONG gone !
Flags: blocking1.7a?
Flags: blocking1.6?
too late for 1.6. let's try for 1.7.
Flags: blocking1.6? → blocking1.6-
Flags: blocking1.7a? → blocking1.7a-
Product: Browser → Seamonkey
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?
Assignee: bugs → nobody
Status: ASSIGNED → NEW
Priority: P3 → --
QA Contact: bugzilla → prefs
Target Milestone: mozilla1.1alpha → ---
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
Status: NEW → UNCONFIRMED
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
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
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
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
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
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
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
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → EXPIRED
Duping against where the action will happen, eventually.
Resolution: EXPIRED → DUPLICATE
Duplicate of bug: 539738
You need to log in before you can comment on or make changes to this bug.