browser show the response on a single line
nick.ager at gmail.com
Sun Aug 7 10:40:20 UTC 2011
I wonder if other people suffer from the same problem when debugging
Seaside's response is viewed by browsers as a string without line-breaks.
Normally this isn't a problem as the browser "pretty-prints" the output when
inspecting the html.
the script debugger (I'm currently using Mac Safari) shows the output as a
generated errors ("syntax error: line 1"!!) or to set meaningful
I've discovered that calling #withInternetLineEndings on the file-library
string results in browsers interpreting the line-endings as expected.
Locally when I'm debugging I've created a class derived from WAHtmlDocument,
which overrides #nextPutAll:
super nextPutAll: aString withInternetLineEndings
and I modify WAFileLibrary>>#handle: modifying the WAResponse>>#document:
document: ((self documentForFile: fileName) withInternetLineEndings)
Is there a better solution? Are there easier workarounds, browser settings
I created an issue for this problem:
Though if there are easy workaround that I've missed, I'd be delighted to
close the issue.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the seaside