Closed
Bug 158333
Opened 22 years ago
Closed 14 years ago
When Mail Start Page is disabled in preferences, Go -> Mail Start Page just hides headers
Categories
(SeaMonkey :: MailNews: Message Display, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: neil, Unassigned)
References
Details
(Keywords: polish, regression)
Attachments
(2 files)
2.19 KB,
patch
|
Details | Diff | Splinter Review | |
2.02 KB,
patch
|
Details | Diff | Splinter Review |
Using Build ID: 2002071704
Steps to reproduce problem:
1. In Mail & Newsgroups preferences, disable the start page.
2. Read a message
3. Go -> Mail Start Page
Actual results: headers are removed
Expected results: a) start page loads or b) menuitem is disabled
But which?
a. some people like the news page but don't want it starting when they start mail.
Keywords: regression
Reporter | ||
Comment 2•22 years ago
|
||
>Using Build ID: 2002071704
This is a white lie, because I have fixed Go -> Mail Start Page in my build for
when mail start page is enabled in preferences (see bug 158028).
Reporter | ||
Comment 3•22 years ago
|
||
Reporter | ||
Comment 4•22 years ago
|
||
The patch depends on my patch to bug 158028.
Reporter | ||
Comment 5•22 years ago
|
||
timeless, note that disabling the page currently disables the URL in prefs...
The pref states,
"When mail launches, show the start page in the message area".
So, i would expect the mail start page to still be available if the user
selects the menu item, just not shown by default on startup.
>Expected results: a) start page loads or b) menuitem is disabled
a. :-)
Reporter | ||
Comment 7•22 years ago
|
||
Although if you disable the automatic start page the Go/Mail Start Page is
still active there's no way to change the start page because the field is
disabled...
Updated•20 years ago
|
Product: Browser → Seamonkey
Updated•20 years ago
|
Assignee: sspitzer → mail
Updated•16 years ago
|
Assignee: mail → nobody
QA Contact: esther → message-display
Comment 8•15 years ago
|
||
MASS-CHANGE:
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•15 years ago
|
||
If I understood this report, the current state in SM 1.1.17 and SM 2.0pre is b.
Even when timeless and jglick prefer a., for me it seems, that this was fixed, so I tend to close this Bug as wfm in a few days.
Ever confirmed: false
Comment 10•14 years ago
|
||
Marking WFM as per comment 9. If (!) you reopen, please not to UNCO, and request reviews as needed.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → WORKSFORME
Reporter | ||
Comment 11•14 years ago
|
||
This was fixed by the patch to bug 70466.
Depends on: 70466
Resolution: WORKSFORME → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•