browser show the response on a single line
johan at inceptive.be
Sun Aug 7 10:52:25 UTC 2011
In the latest Chrome, you can choose to 'de-obfuscate source' in the context menu of the script tab in the developer tools.
That solves it mostly for me.
On 07 Aug 2011, at 12:40, Nick Ager wrote:
> 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.
> 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:
> WAHtmlDocumentWithInternetLineEndings>>#nextPutAll: aString
> super nextPutAll: aString withInternetLineEndings
> and I modify WAFileLibrary>>#handle: modifying the WAResponse>>#document: to:
> document: ((self documentForFile: fileName) withInternetLineEndings)
> Is there a better solution? Are there easier workarounds, browser settings etc.
> I created an issue for this problem: http://code.google.com/p/seaside/issues/detail?id=675
> Though if there are easy workaround that I've missed, I'd be delighted to close the issue.
> seaside mailing list
> seaside at lists.squeakfoundation.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the seaside