Closed GoogleCodeExporter closed 9 years ago
It does this simply for readability. Otherwise, if you had 11 tags, they would
all
show up on the same line. I'll send an email to the mailing list to see what
most
users would prefer.
I can definitely add it as a directive (no formatting).
Original comment by arshan.d...@gmail.com
on 2 Jun 2008 at 1:37
The directive sounds good to me, thanks for the prompt response!
Original comment by carlos.a...@gmail.com
on 2 Jun 2008 at 2:21
I second this bug, and I second the directive as a solution.
Original comment by thedownw...@gmail.com
on 6 Jun 2008 at 10:39
I third this bug, and I third the directive as a solution
Original comment by atsouk...@gmail.com
on 9 Jun 2008 at 2:31
I added a change in 1.2 that prevents any OutputFormat changes from taking
place.
However, the CSS serialization is quite separate. Does everyone find this
agreeable?
Original comment by arshan.d...@gmail.com
on 17 Jun 2008 at 6:00
Sounds good to me, I'll try it out!
Original comment by carlos.a...@gmail.com
on 19 Jun 2008 at 2:56
Shouldn't the "formatOutput" directive only set the "lineWidth" and "indenting"
in
lines 170-172 of AntiSamyDOMScanner?. Lines 174 through 177 should be outside
the if
statement that checks if "formatOutput" is set to true (line 169).
I just tried the 1.2 release and if "formatOutput" is null or false, it will
skip the
"omitXmlDeclaration" and "omitDoctypeDeclaration". I saw that after getting the
"finalCleanHTML" in line 199 you strip out the xml declaration, however there's
nothing done for the "omitDoctypeDeclaration". So when I run the example
mentioned
above, I get this back:
javascript <!DOCTYPE HTML PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/WD-html-in-xml/DTD/xhtml1-strict.dtd">
java python
This is because I'm not setting the formatOutput. But then I'd still expect
AntiSamy
to just return:
javascript java python
Original comment by carlos.a...@gmail.com
on 19 Jun 2008 at 5:43
Yes, my logic was screwed up. I have fixed it for the next release.
Original comment by arshan.d...@gmail.com
on 10 Jul 2008 at 12:46
Original issue reported on code.google.com by
carlos.a...@gmail.com
on 30 May 2008 at 1:45