Closed Bug 245839 Opened 20 years ago Closed 20 years ago

XHTML img tags are re-written wrong when Save As, Web Page, Complete is used

Categories

(Core Graveyard :: File Handling, defect)

Product:
Core Graveyard
Component:
File Handling
Platform:
x86
Windows XP
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
VERIFIED DUPLICATE of bug 205264

People

(Reporter: billy, Unassigned)

References

(
URL
)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040206 Firefox/0.8 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040206 Firefox/0.8 When saving the output of a php script that is formatted as XHTML 1.0 Strict: "<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">"> using the Save As, Web Page, complete option, the img tags are damaged. The "/" preceding the end of the img tag is stripped out, rendering the document non XHTML 1.0 Strict compliant. eg - <img src="http://remotehost/foo.gif"/> becomes <img src="localpath/foo.gif"> Reproducible: Always Steps to Reproduce: 1. Browse to a php script with XHTML 1.0 Strict output 2. View the remote page source to verify the img tags are correct 2. Save the page as Web Page, complete 3. View the local page source and the img tags are broken Actual Results: img tags are missing the "/" before the end of the tag, as specified by XHTML 1.0 Strict, rendering the document non-compliant. Expected Results: The "/" preceding the end of the img tag should have been preserved, to keep the page XHTML 1.0 Strict compliant.
Also occurs in Moz 1.8a1, not Firefox specific. ->Browser
Assignee: bugs → file-handling
Product: Firefox → Browser
QA Contact: aebrahim → ian
Version: unspecified → Trunk
6 Content-Type: text/html; charset=ISO-8859-1 --> that page is not XHTML, it's HTML. see bug 120556 comment 6. mozilla is behaving as expected.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
(In reply to comment #2) > 6 Content-Type: text/html; charset=ISO-8859-1 > > --> that page is not XHTML, it's HTML. > > see bug 120556 comment 6. mozilla is behaving as expected. But the document doctype clearly specifies the file is xhtml strict, regardless of what the web server delivers the page as. Is that really the behavior it should have?
according to the html working group, yes. In any case the DOCTYPE can't reliably be used to detect XHTML, as discussed in http://www.hixie.ch/advocacy/xhtml
Status: RESOLVED → UNCONFIRMED
Resolution: INVALID → ---
*** This bug has been marked as a duplicate of 205264 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago → 20 years ago
Resolution: --- → DUPLICATE
Status: RESOLVED → VERIFIED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.