Closed
Bug 185057
Opened 22 years ago
Closed 22 years ago
if an image or link is moved inside a page the 'URL is relative to page location' is ignored
Categories
(Core :: DOM: Editor, defect)
Core
DOM: Editor
Tracking
()
People
(Reporter: miha, Assigned: mozeditor)
Details
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.2.1) Gecko/20021130
Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.2.1) Gecko/20021130
If the image or link is moved by drag&drop the image or link loose information
about URL being relative to the page location. The result is 'file:///...' in
the source code and that leads to broken links.
Reproducible: Always
Steps to Reproduce:
1. Open a local html file in composer. The file should include an image, e.g
<IMG SRC="image.gif">
2. Select the image and drag&drop it to a new location.
3. The source code will change to e.g. <IMG
SRC="file:///C:/My%20Documents/image.gif">
Actual Results:
The image is now visible on the users system, but when the user saves the html
file and uploads it with FTP the image is not visible anymore (the link is wrong).
Expected Results:
The normal behavour would be to preserve the location as it was and not change
the relative location setting.
Comment 1•22 years ago
|
||
Same problem on windowsXP mozilla 1.2.1.
The background image is not saved as relative location "URL is relative.." wne
requested.
Instead it is always saved with full local file description, ex.
"file:///C:/windows....". Then if you copy this file to your web page it views
correctly for you, but no one else since they can't access the image file due to
the bad link.
Comment 2•22 years ago
|
||
-->core
jfrancis--this is probably a duplicate of another bug on your plate
Assignee: syd → jfrancis
Component: Editor: Composer → Editor: Core
OS: Windows 98 → All
Hardware: PC → All
Whiteboard: DUPEME
Assignee | ||
Comment 3•22 years ago
|
||
*** This bug has been marked as a duplicate of 32768 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•