Closed
Bug 219135
Opened 21 years ago
Closed 21 years ago
A posibility to automatically remove dead links (bookmarks) in Bookmarks Manager
Categories
(SeaMonkey :: Bookmarks & History, enhancement)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 171467
People
(Reporter: przemsen, Assigned: p_ch)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624
There should be an option in Bookmarks Manager which automatically removes
bookmarks with dead links
Reproducible: Always
Steps to Reproduce:
1.
2.
3.
Comment 1•21 years ago
|
||
how should Mozilla know if your link is dead ?
(could be a temporary server or connection problem..)
dupe of either 171467 or the one it depends on, bug 8648.
*** This bug has been marked as a duplicate of 171467 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
Reporter | ||
Comment 3•21 years ago
|
||
>(could be a temporary server or connection problem..)
of course it could be a temporary problem, however the page could also be removed.
>how should Mozilla know if your link is dead ?
simply trying to conect to the server or trying pinging it. If there is no
response or error 404 occurs Mozilla should automatically remove such dead
bookmark. I think there should be an option which verifies all bookmarks this
way, displays bookmarks which seem to be dead, and allows user to remove all
listed bookmarks with one click.
Status: RESOLVED → UNCONFIRMED
Resolution: DUPLICATE → ---
>bookmark. I think there should be an option which verifies all bookmarks this
>way, displays bookmarks which seem to be dead, and allows user to remove all
>listed bookmarks with one click.
Well since you put it that way, it's definitely a duplicate of bug 171467.
*** This bug has been marked as a duplicate of 171467 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago → 21 years ago
Resolution: --- → DUPLICATE
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•