336399 - When saving xhtml pages, closed xhtml tags are opened by Camino

Status: VERIFIED DUPLICATE of bug 120556

(Camino Graveyard :: General, defect)

Description

[Sophie G]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.0.3) Gecko/20060427 Camino/1.0.1
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.0.3) Gecko/20060427 Camino/1.0.1

Viewing source on the page, the xhtml tags like meta are closed with a trailing slash. When I save as Html complete, these xhtml tags end up opened.

<meta http-equiv="content-type" content="text/html; charset=utf-8" />
becomes
<meta http-equiv="content-type" content="text/html; charset=utf-8">

I've tried on various pages, including some that advertise serving xhtml content as application/xhtml+xml, like http://www.w3.org/2003/01/xhtml-mimetype/content-negotiation, and the save command always has the same effect.

The save html source only command doesn't display this behaviour.

Reproducible: Always

Steps to Reproduce:
1.Save page as html complete
2.Compare source of page and saved page
3.

Actual Results:  
Closed tags are opened

Comment 1

[Chris Lawson (gone)]

If this does happen -- and I haven't tested it -- it's unlikely to be a bug in Camino, as I'm fairly certain our page-saving code is in Core.

To be fair to the Core devs, though, "HTML complete" does not mean the same thing as "XHTML complete". I agree that "complete" does seem to say "don't screw around with the source code I just told you to save", though.

cl

Comment 2

[Stuart Morgan]

Dup of 120556.

Saving as HTML complete has to change the source, in order to point to the saved local resources; it's not necessarily designed to give you the same source, just the same DOM when loaded.  The reason this is correct behavior is that that page is *not* XHTML, but HTML--the determining factor is the content type it is served as, which here, as almost everywhere else, is text/html. If the page were served as XHTML, you wouldn't see this behavior.

*** This bug has been marked as a duplicate of 120556 ***

Comment 3

[Sophie G]

(In reply to comment #2)
> If
> the page were served as XHTML, you wouldn't see this behavior.
> 
That's why I took the pain to check with this page :
http://www.w3.org/2003/01/xhtml-mimetype/content-negotiation
Which illustrates content negociation for serving  pages as application/xhtml+xml.

This page is modified in the same way by the browser. Maybe it's not served as application/xhtml+xml, but let me doubt about it.

In Camino, it is impossible to save the page with a .xhtml extension.

Comment 4

[Stuart Morgan]

$ curl -I http://www.w3.org/2003/01/xhtml-mimetype/content-negotiation
HTTP/1.1 200 OK
Date: Wed, 03 May 2006 16:30:51 GMT
Server: Apache/1.3.33 (Unix) PHP/4.3.10
[snip]
Content-Type: text/html; charset=iso-8859-1