Open Bug 229702 Opened 21 years ago Updated 16 years ago

Should not have "Save Link As" option on links whose protocols we can't handle

Categories

(SeaMonkey :: UI Design, defect)

x86
Windows 98
defect
Not set
normal

Tracking

(Not tracked)

People

(Reporter: bzbarsky, Unassigned)

References

()

Details

BUILD: any recent-ish windows build (using 2003-12-28-17 here). 

STEPS TO REPRODUCE:

1)  Make sure you have Windows Media Player installed
2)  Find a link to an mms file;  mms://this_is_such_a_link
3)  Right click on the link
4)  Select "save link as"
5)  Pick a spot to save to

EXPECTED RESULTS:  Good question!

ACTUAL RESULTS:  Windows Media Player opens and plays the movie (if it's a link
to a real movie)

SUGGESTED RESOLUTION:
I suggest we not show "Save link as" in the context menu for links that we can't
save.  The problem is determining such links.   I guess getting the protocol
handler for the protocol off the IOService and then seeing whether it QIs to
nsIExternalProtocolHandler would work.  darin, does that seem reasonable?

Scott, I'm ccing you because it looks like tbird forked nsContextMenu.js so
whatever we do here may need porting over there...
Well, bugzilla didn't linkify the link in steps to reproduce... but it did
linkify the one in the URL field, so use that one to test.  ;)
BTW, IE5 pops up a "Download could not complete!" error :-)
That's vastly preferable to what we do.. ;)
Product: Core → Mozilla Application Suite
Filter "spam" on "guifeatures-nobody-20080610".
Assignee: guifeatures → nobody
QA Contact: guifeatures
Component: XP Apps: GUI Features → UI Design
You need to log in before you can comment on or make changes to this bug.