Hi,<div><br></div><div>I wonder if other people suffer from the same problem when debugging javascript:<br><br>Seaside's response is viewed by browsers as a string without line-breaks.<br>Normally this isn't a problem as the browser "pretty-prints" the output when inspecting the html.<br>
However when debugging javascript, either inline or within a file-library the script debugger (I'm currently using Mac Safari) shows the output as a single line - which makes it impossible to interpret any javascript generated errors ("syntax error: line 1"!!) or to set meaningful breakpoints.<br>
<br>I've discovered that calling #withInternetLineEndings on the file-library string results in browsers interpreting the line-endings as expected.<br><br>Locally when I'm debugging I've created a class derived from WAHtmlDocument, which overrides #nextPutAll: <br>
WAHtmlDocumentWithInternetLineEndings>>#nextPutAll: aString<br> super nextPutAll: aString withInternetLineEndings<br><br>and I modify WAFileLibrary>>#handle: modifying the WAResponse>>#document: to: <br>
document: ((self documentForFile: fileName) withInternetLineEndings)<br><br>Is there a better solution? Are there easier workarounds, browser settings etc.<br></div><div><br></div><div>I created an issue for this problem: <a href="http://code.google.com/p/seaside/issues/detail?id=675">http://code.google.com/p/seaside/issues/detail?id=675</a></div>
<div><br></div><div>Though if there are easy workaround that I've missed, I'd be delighted to close the issue.</div><div><br></div><div>Thanks</div><div><br></div><div>Nick</div>