Open Bug 536099 Opened 16 years ago Updated 5 years ago

Seamonkey Composer, when saving after editing an existing page, new images are not included in the save

Categories

(SeaMonkey :: Composer, defect)

x86_64
All
defect
Not set
normal

Tracking

(Not tracked)

People

(Reporter: bugzilla, Unassigned)

Details

(Whiteboard: [Halloween2011Bug]DUPEME)

User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.6) Gecko/20091201 Firefox/3.5.6 Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.6) Gecko/20091206 SeaMonkey/2.0.1 When editing an existing html page with Seamonkey Composer, and new images are added, when the page is saved, the new images keep their relative (or absolute) paths within the saved html file (src= is file:///local/path/to/image/I/added/file.jpg, or ../../../path/to/image.jpg for example), and not re-written to src="filename.jpg". If I "Save As" the same filename, behaviour is the same as Save - the images are not handled correctly. If I "Save As" into a new /path/to/filename.html, the image is copied into the new /path/to/ directory, and the src= link in the html file is properly re-written to point to the local (same directory) copy of that file as would be expected. Reproducible: Always Steps to Reproduce: 1. Edit existing html page 2. Insert new image from hard drive (outside of webpage root) 3. Save page 4. Observe that newly added image files are not placed into directory containing html file 5. Copy contents to webserver (manual, or via 'publish') 6. Observe same result - new images are not transferred to webserver. Actual Results: Images that were added were not available online. Expected Results: Images should have been saved into the directory with the page undergoing the edit. Both existing, and new images should be placed into the target directory. "is the image file there? Yes? Good, next." "Is the next file there? No? Copy it from the source location into the target directory"
The order of the steps Save and Publish affect the result, see bug 327579 and bug 327578.
Version: unspecified → SeaMonkey 2.0 Branch
Could you check this against SM2.3 and see if the issue is still present?
Issue still here Build identifier: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0a1) Gecko/20111017 Firefox/10.0a1 SeaMonkey/2.7a1
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Mac OS X → All
Whiteboard: [Halloween2011Bug]DUPEME
Version: SeaMonkey 2.0 Branch → Trunk
You need to log in before you can comment on or make changes to this bug.