Closed docbobo closed 11 years ago
The escaping in SLiM used to be very inconsistent. With the latest version I tried to make it consistent. As a rule of thumb all text will be escaped by FitNesse, so characters like <
and >
will be rendered properly. Also it releases the fixture writer from doing all sorts of escaping. I am aware that this will do a double escape, in case the fixture also does escaping. This, however, seems better than doing no escaping at all (which can really mess up test output).
Duplicate of #274.
I tried to give FitNesse a try for the first time yesterday, together with RestFixture. Unfortunately, the results are not rendered correctly because the RestFixture results seem to be HTML escaped twice - once on the RestFixture/SlimServer side and once on the Fitnesse side.
Using 'git bisect', it seems that the following commit is the culprit:
I did read somewhere that SLIM response should be already HTML escaped but failed to find this quote again. Can anybody confirm whether the SLIM response should already be escaped or not? This would determine whether this needs to be fixed on the FitNesse side or on the RestFixture side.
Thanks