Closed Bug 193060 Opened 23 years ago Closed 23 years ago

View Selection Source displays "<br />" tags as "<br>"

Categories

(Core Graveyard :: View Source, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 190947

People

(Reporter: bugzilla, Assigned: doronr)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3b) Gecko/20030210 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3b) Gecko/20030210 When viewing selection source of text on a page with XHTML-style break tags (<br />), the source viewer for some reason converts the tags to HTML-style (<br>). This could cause quite a bit of confusion, since the source being displayed doesn't represent the actual source. Reproducible: Always Steps to Reproduce: 1. Select some text on a webpage containing XHTML-style break tags. 2. Right-click and choose "View Selection Source" Actual Results: XHTML-style break tags were displayed as HTML-style break tags. Expected Results: The selection source should be displayed as is, unmodified.
View selection source never represents the actual source (that would be impossible to implement if you consider DOM modifications) -- it is a serialization of the DOM. That means that on an HTML page (not XML) it should be dropping the '/' from <br />
That makes sense. Even so, it caused me to waste a good twenty minutes trying to figure out why my web application was generating incorrect XHTML. It would be nice if the source viewer would let the user know that they're not necessarily seeing the actual source in this circumstance.
-> head over to that bug 190947 if you have a suggestion about a simple and intuitive way to remind users that the source comes from the DOM. *** This bug has been marked as a duplicate of 190947 ***
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Product: Browser → Seamonkey
This could also be considered a dup of bug 233386.
Product: SeaMonkey → Core Graveyard
You need to log in before you can comment on or make changes to this bug.