Closed
Bug 184108
Opened 22 years ago
Closed 21 years ago
Save As <<filename>> without <<.html>> extention result is a html file <<filename>> and a directory <<_files>>
Categories
(Core Graveyard :: File Handling, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: froelants, Assigned: law)
References
Details
Attachments
(2 files)
1.04 KB,
patch
|
Biesinger
:
review+
bzbarsky
:
superreview+
|
Details | Diff | Splinter Review |
1.39 KB,
patch
|
timeless
:
review+
bzbarsky
:
superreview+
|
Details | Diff | Splinter Review |
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021130 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021130 When I saved a complete webpage with mozilla 1.11 using the "Save as" menuitem and I entered only the name of the page without .html extention it resulted in a html file filename.html and a directory filename_files . This version does that any more. I need to enter the complete name. Saving two pages in one directory results in problems, the second time does the directory _files already exists. Reproducible: Always Steps to Reproduce: 1.menu: file - Save As 2.enter <<filename>> without .html Actual Results: a html file filename a directory _files Expected Results: a html file filename.html or filename a directory filename_files I'm using Suse8.0 and mozilla is installed in /opt/mozilla
Comment 1•22 years ago
|
||
==> File Handling
Assignee: dougt → law
Component: Networking: File → File Handling
QA Contact: benc → petersen
I don't have Suse but I can verify with RH on a recent build. From the looks of it, it is due to the file selector not putting the proper file extension on the document name when it tells it to save. The perist object doesn't append an extension for itself, expecting the caller to do that. Reassigning to module owner.
Assignee: adamlock → law
Status: UNCONFIRMED → NEW
Ever confirmed: true
Attachment #124053 -
Flags: superreview?(bz-bugspam)
Attachment #124053 -
Flags: review?(cbiesinger)
Updated•21 years ago
|
Attachment #124053 -
Flags: superreview?(bz-bugspam) → superreview+
Comment 5•21 years ago
|
||
Comment on attachment 124053 [details] [diff] [review] fix r+ because this code is broken; but it doesn't fix this bug. I will attach a patch that does fix it.
Attachment #124053 -
Flags: review?(cbiesinger) → review+
Comment 6•21 years ago
|
||
Comment 7•21 years ago
|
||
Comment on attachment 124545 [details] [diff] [review] additional fix bz - this is a really small patch, would be great if you could find the time to sr it
Attachment #124545 -
Flags: superreview?(bz-bugspam)
Attachment #124545 -
Flags: review?(timeless)
Attachment #124545 -
Flags: review?(timeless) → review+
Comment 8•21 years ago
|
||
Comment on attachment 124545 [details] [diff] [review] additional fix sr=me, but this looks identical to timeless' patch, so if you were going to make other changes, you forgot to...
Attachment #124545 -
Flags: superreview?(bz-bugspam) → superreview+
Comment 9•21 years ago
|
||
bz: yeah, it is identical, but in a different file :)
Comment 10•21 years ago
|
||
Ah. Yeah, we need both changed... friggin' code duplication. :(
Comment 11•21 years ago
|
||
checked in
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
Updated•21 years ago
|
Flags: blocking1.4?
Updated•21 years ago
|
Flags: blocking1.4?
Comment 12•21 years ago
|
||
*** Bug 216818 has been marked as a duplicate of this bug. ***
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
•