Closed
Bug 124680
Opened 22 years ago
Closed 22 years ago
doing save image: the context menu uses a different algorithm for parsing the url to get the filename
Categories
(Core Graveyard :: File Handling, defect, P4)
Core Graveyard
File Handling
Tracking
(Not tracked)
VERIFIED
WORKSFORME
mozilla1.1alpha
People
(Reporter: mozbugz, Assigned: bzbarsky)
References
()
Details
from bug 115176. save image context menu item, still pulls up the script, and not the filename that is suggested in the context menu itself. ------- Additional Comment #144 From Boris Zbarsky 2002-02-09 08:06 ------- That would be because the context menu uses a different algorithm for parsing the url to get the filename... ------- Additional Comment #145 From Dan Tobias 2002-02-09 08:13 ------- The site cited in comment 143 is a bit of a "degenerate case" for parsing filenames out of URLs... they have some odd naming systems there. For instance, the URL cited ends in ".jpg" but is actually an HTML page -- fortunately, their server has the sense to serve it with the correct MIME type, but it still wouldn't surprise me all that much if MSIE had a cow about it given its infamous MIME second-guessing. The image in question does indeed have a script name as its filename, with the image name being a parameter to it. One can forgive a browser if it tries to save the resulting file by the script name instead of the parameter. However, the behavior of showing one name in the context menu and another when you actually save it is rather bizarre and ought to be made consistent (even if, on some sites, that might result in it being consistently wrong). ------- Additional Comment #146 From johann@ai.univie.ac.at 2002-02-09 08:19 ------- When doing a "Save Page" or "Save Image" (not from the context menu) when displaying URL http://www.shacknews.com/images/image-o-matic.x?halo/031201_halo_3.jpg it shows "image-o-matic.x" as the proposed filename. So its not just the differemt algorithm of the context menu then? ------- Additional Comment #147 From Boris Zbarsky 2002-02-09 08:24 ------- Yes. It is. The context menu shows "031201_halo_3.jpg". Everything else shows "image-o-matic.x" (all the save methods do). That would be "just the differemt [sic] algorithm of the context menu".
Reporter | ||
Comment 1•22 years ago
|
||
updating summary to long description. Thanks Boris. You are the File handling guru. The other issue I see with this is, let me know if you want me to file a report for this: on this type of save with .jpeg, save dialog is not adding the extention to saved filename if you dont supply it on w2k using same URL.
Summary: the context menu uses a different algorithm for parsing → doing save image: the context menu uses a different algorithm for parsing the url to get the filename
Assignee | ||
Comment 2•22 years ago
|
||
Taking this to get it off Bill's plate
Assignee: law → bzbarsky
OS: Windows 2000 → All
Hardware: PC → All
Target Milestone: Future → mozilla1.1
Assignee | ||
Updated•22 years ago
|
Priority: -- → P4
Assignee | ||
Comment 3•22 years ago
|
||
Well.. the context menu no longer has a filename, so resolving this worksforme. If bug 136110 gets fixed and the algorithm is still different, please reopen.
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → WORKSFORME
Comment 4•22 years ago
|
||
mass-verifying WorksForMe bugs. reopen only if this bug is still a problem with a *recent trunk build*. mail search string for bugspam: AchilleaMillefolium
Status: RESOLVED → VERIFIED
Updated•8 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•