Closed (outdated)
Project:
Drupal core
Version:
6.6
Component:
base system
Priority:
Minor
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
28 Feb 2010 at 19:53 UTC
Updated:
2 Mar 2016 at 22:18 UTC
Jump to comment: Most recent
Comments
Comment #1
enterprisereview commentedComment #2
dman commentedDrupal cleaning up your code?
You sure it's not a WYSIWYG or input filter issue?
Even within a PRE, that's not valid XHTML (though you could have got away with it in HTML4)
If doing real XMP, you should probably use a namespace prefix, but if you just want to create valid XHTML that a browser can use, then you could use
<xmp>OR use a codefilter processor that will correctly render your verbatim code in a way that a browser won't choke on, eg by escaping it with entities.
You'd have to describe your setup a bit more - are you using a WYSIWYG? and what input format and input filters are you using? And is that result you pasted an actual view-source or just from the DOM inspector (which lies)?
Comment #3
enterprisereview commentedno wysiwig
no filters, default set up.
source view
The work arounds, yes, I have done that, but I am raising the fact the clean up needs to understand pre and xmp tags.