debugging javascript within browsers is hard when the browser show the response on a single line

Hi,

I wonder if other people suffer from the same problem when debugging javascript:

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.
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.

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.

Thanks

Nick

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

Hi Johan,

 

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.

Hmm I'm using Chrome version 13.0.782.107 which doesn't seem to include 'de-obfuscate source' option and it seems it's missing for others: http://www.google.com/support/forum/p/Chrome/thread?tid=648734bd79c17a69&hl=en

Pior to the 'de-obfuscate source'  option - did you have any other work-arounds?

Nick

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

Hi Nick,

Ah yes...

It's not missing. It's now called 'pretty print' and is the '{ }' button in the bottom bar of dev tool.

Prior to that, I had no workarounds, but most (90%) of our javascript code is contained in external files, which show nicely in the scripts pane (when not minified).

Johan

On 07 Aug 2011, at 13:11, Nick Ager wrote:

Hi Johan,

 

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.

Hmm I'm using Chrome version 13.0.782.107 which doesn't seem to include 'de-obfuscate source' option and it seems it's missing for others: http://www.google.com/support/forum/p/Chrome/thread?tid=648734bd79c17a69&hl=en

Pior to the 'de-obfuscate source'  option - did you have any other work-arounds?

Nick

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

But apart from that, I think it would be a great option to be able to choose for 'minified' or 'non minified' generated javascript in Seaside…

On 07 Aug 2011, at 13:18, Johan Brichau wrote:

Hi Nick,

Ah yes...

It's not missing. It's now called 'pretty print' and is the '{ }' button in the bottom bar of dev tool.

Prior to that, I had no workarounds, but most (90%) of our javascript code is contained in external files, which show nicely in the scripts pane (when not minified).

Johan

On 07 Aug 2011, at 13:11, Nick Ager wrote:

Hi Johan,

 

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.

Hmm I'm using Chrome version 13.0.782.107 which doesn't seem to include 'de-obfuscate source' option and it seems it's missing for others: http://www.google.com/support/forum/p/Chrome/thread?tid=648734bd79c17a69&hl=en

Pior to the 'de-obfuscate source'  option - did you have any other work-arounds?

Nick

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside