Subcription Windows Should not be Resizable Below Minimum

RESOLVED EXPIRED

Status

SeaMonkey
MailNews: Message Display
RESOLVED EXPIRED
17 years ago
8 years ago

People

(Reporter: Phil Miller, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

17 years ago
In MailNews, when subscribing to newsgroups on the selected news server,
clicking subscribe in a few different places in the UI opens the "Subscribe"
dialog box. This window is completely resizable, to the point where only the
Title and the close button are visible.  It should have a minimum size set, both
vertically and horizontally, if it should be resizable at all.
According to the spec, (http://www.mozilla.org/mailnews/specs/subscribe/), this
window should be resizable, but dimensions for min height/width aren't yet
specified.  Jennifer, Seth, comments?
OS: Windows 98 → All
Hardware: PC → All

Comment 2

17 years ago
A minimum size is probably a good idea. Open to suggestions what that size 
should be.
(Reporter)

Comment 3

17 years ago
258 pixels is the minimum height before Windows starts drawing the window incorrectly. Specifically, the OK and cancel buttons are cut off as the window is resized vertically. I'm not sure if this is true on other platforms, or under different display environments.
The minimum width can be lower than 300 pixels, but below that point, the window is not very useful for seeing what your are subscribed to.

Just a few other nits, although they're not exactly part of this bug: First, the column heading for the name of the group should be something shorter, like simply "Group" or "Name". Second, the "Subscribe" column should be to the left of the name column, should be of a fixed minimum width needed to display the check or dot, and should be unlabeled. Third, the messages column should be optional, and should have some way of disabling it.
Confirming bug.
Status: UNCONFIRMED → NEW
Ever confirmed: true

Updated

17 years ago
Status: NEW → ASSIGNED
Target Milestone: --- → Future
I've been asked to mass-check bugs with no TM and priority, as to their
validity.  This bug still exits on the latest trunk.

Comment 6

17 years ago
Either this is dupe or depend of http://bugzilla.mozilla.org/show_bug.cgi?id=74940
(Reporter)

Comment 7

16 years ago
These seems as though it would depend on fixing bug 74940, as it requires
capabilities that would be gained only form fixing that one. I'm marking it for
now, as there have been no comment from the owner to a different effect, and
this is not a dupe, as this is a specific case where we need to use what's
implemented in 74940.
Depends on: 74940
Product: Browser → Seamonkey

Updated

13 years ago
Assignee: sspitzer → mail
Status: ASSIGNED → NEW

Updated

10 years ago
Component: MailNews: Subscribe → MailNews: Message Display
QA Contact: stephend → search
Assignee: mail → nobody
QA Contact: search → message-display
Target Milestone: Future → ---

Comment 8

9 years ago
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

Comment 9

9 years ago
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 10

9 years ago
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
Group: core-security

Comment 11

9 years ago
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

Updated

9 years ago
Group: core-security

Comment 12

8 years ago
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
Last Resolved: 8 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.