Closed
Bug 171974
Opened 24 years ago
Closed 24 years ago
removing expired articles NEEDS WORK
Categories
(MailNews Core :: Networking: NNTP, defect)
Tracking
(Not tracked)
VERIFIED
DUPLICATE
of bug 129574
People
(Reporter: hunterp, Assigned: Bienvenu)
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1b) Gecko/20020830
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1b) Gecko/20020830
4 issues:
-removing expired articles spawns a new window; this is not asked for.
-its very slow performance
-you should be able to selectively remove articles
-there should be a button for it, instead of having to search around for an
actual expired article and getting "dialogue text" there.
Reproducible: Always
Steps to Reproduce:
1.
2.
3.
| Assignee | ||
Comment 1•24 years ago
|
||
none of this has anything to do with the mail database. Several of these issues
are covered in other bugs. I can't imagine why you'd selectively want to remove
expired articles, since the only reason they appear is because there are gaps in
the article sequences - if the expired article is before any non-expired
articles in the sequence, it automatically gets removed.
Component: Mail Database → Networking: News
Updated•24 years ago
|
QA Contact: gayatri → stephend
All of the issues are covered indeed, except for the second issue of performance.
See bug 98534, bug 129574 and bug 106241.
Since we only desire one issue per bug report, I'm duping to the first issue you
brought to our attention, bug 106241.
*** This bug has been marked as a duplicate of 106241 ***
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
Whoops, that _would_ be, bug 129574, sorry.
Status: RESOLVED → UNCONFIRMED
Resolution: DUPLICATE → ---
*** This bug has been marked as a duplicate of 129574 ***
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago → 24 years ago
Resolution: --- → DUPLICATE
verified dup
Status: RESOLVED → VERIFIED
Updated•21 years ago
|
Product: MailNews → Core
Updated•17 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•