Mozilla should have a feature to check is the link available or not

RESOLVED EXPIRED

Status

SeaMonkey
UI Design
--
enhancement
RESOLVED EXPIRED
17 years ago
8 years ago

People

(Reporter: Alexander Hessentswey, Assigned: Samir Gehani)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

17 years ago
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.7+) Gecko/20020116
BuildID:    2002011604

Mozilla should have a feature to check is the link available or not.
For example:
If you click on a link, holding the Alt key, you will get a message in the
statusbar, like that:
"link couldn't be found (nothing in cache)"
"link was found (nothing in cache)"
"link couldn't be found (copy in cache exists)"
"link was found (copy in cache exists)"

Updated

17 years ago
OS: Windows 95 → All
Hardware: PC → All

Comment 1

17 years ago
Thanks, but no time to consider new work in this release cycle.  ->future
Target Milestone: --- → Future
shouldn't this belong in networking:cache? punt as needed...
Assignee: trudelle → gordon
Component: XP Apps → Networking: Cache
QA Contact: sairuh → tever

Comment 3

17 years ago
No, this wouldn't be a cache feature, it would be a UI feature that might use
the cache service.  It probably would also make XPCOM calls, but I wouldn't
assign it to the XPCOM component.

Changing component back to XP APPs.
Component: Networking: Cache → XP Apps

Comment 4

17 years ago
It is XPApps, just not worth doing.
Assignee: gordon → trudelle
QA Contact: tever → sairuh
Confirming RFE since it's already been futured
Status: UNCONFIRMED → NEW
Ever confirmed: true

Comment 6

16 years ago
Mass moving all of my open Nav/toolkit bugs to new owner.
Assignee: trudelle → sgehani
Product: Core → Mozilla Application Suite

Comment 7

9 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 8

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.