Closed Bug 303177 Opened 19 years ago Closed 19 years ago

"Copy XML" menu option in DOM Inspector copies nodes in Uppercase

Categories

(Other Applications :: DOM Inspector, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: rhaddon, Unassigned)

References

()

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6

This is not a bug but a mistake in the DOM Inspector. When you choose the option
"Copy XML" the XML that is copied to the clipboard is not proper XML as all the
elements are in Uppercase.

I am using this function in order to save the file and test it on the W3C
validator to make sure my dynamic content is complient too. The W3C validator
will not recognise the xhtml tags in uppercase.

Reproducible: Always

Steps to Reproduce:
1. Open DOM Inspector on any XHTML page
2. Right click HTML node and choose "Copy XML"
3. Paste to a text editor or similar and observe the Uppercase Nodes

Actual Results:  
Exactly as I describe above.

Expected Results:  
it should output the tags in Lowercase as per the original source and the W3C
standard for XHTML
Assignee: nobody → dom-inspector
Component: General → DOM Inspector
Product: Firefox → Other Applications
QA Contact: general → timeless
WFM Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050719
Firefox/1.0.6

Are you absolutely certain the webpage was served as application/xhtml+xml?  If
it was served as text/html, then the behavior was correct.  HTML (which is what
XHTML is treated as under text/html) has uppercase tags to the DOM.
(In reply to comment #1)
> WFM Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050719
> Firefox/1.0.6
> 
> Are you absolutely certain the webpage was served as application/xhtml+xml?  If
> it was served as text/html, then the behavior was correct.  HTML (which is what
> XHTML is treated as under text/html) has uppercase tags to the DOM.

You are correct, the page was served as text/html. I was not aware this was what
decided the DOM layout.

Thanks
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → INVALID
Assignee: dom-inspector → nobody
QA Contact: timeless → dom-inspector
You need to log in before you can comment on or make changes to this bug.