Repository navigation
Avoid escaping \n to minimize pollution - #17
Conversation
|
@cdsmith Thoughts? |
|
One note: modifying |
|
@mightybyte I don't know of any problems. If the tests pass, then it is probably okay. If I'd done this on purpose, there would be a test to guarantee it. |
|
It does look like that change benefitted the HTML rendering as well - when I visit my site: Serendipitous running that code, I now see no extraneous My previous report that it didn't change HTML must have been based on cached data in Chrome or something along those lines. I have caches turned off, but I've found Chrome to sometimes be hyper-aggressive about that sort of thing. |
|
Great! That was really perplexing me. |
These changes correct the
pollution for xtpl (XML) templates. This accommodates XML parsers that require well-formed XML without extra data following the closure of the root element (e.g., RSS).This does not address the
pollution in HTML files. I'm inclined to think that's coming from another library (perhaps Blaze Builder) as I can't find any source for it in this library.This change does not affect the successful execution of the test suite: