Re: JavaScript errors in dynamic host page

I have now. :-)

The two versions differ only in this: the static version has these
HTTP headers, whereas the dynamic version does not.

Accept-Ranges: bytes
ETag: W/"4071-1302051328262"
Last-Modified: Wed, 06 Apr 2011 00:55:28 GMT
Content-Type: text/html

I will make the dynamic version produce these headers also. Do you
think their omission is to blame?

On Apr 6, 8:03 pm, Paul Robinson <ukcue...@gmail.com> wrote:
> Have you used firebug to check that the response body *and* the http headers are the same in the static and dynamic versions?
>
> On 06/04/11 08:54, David Pinn wrote:
>
>
>
>
>
>
>
> > Oops! Bad spelling. The last paragraph should read:
>
> > I'm flummoxed as to the reason for these error messages. If I turn
> > the
> > page into a static HTML page - my app won't work properly in this
> > fashion, but just for the sake of testing - then everything works
> > just
> > fine. Can you help me understand what's going on here, and how I
> > might
> > get around it?
>
> > On Apr 6, 5:49 pm, David Pinn<dp...@byandlarge.net>  wrote:
> >> I'm trying to implement the dynamic host page pattern as described
> >> here:http://code.google.com/webtoolkit/articles/dynamic_host_page.html;
> >> but I"m finding that the module won't load. I suspect that the
> >> existence of two JavaScript errors in GWT-generated code are the
> >> reason.
>
> >> When running the application inside Dev Mode, the following two
> >> JavaScript errors are found:
>
> >> 1. Uncaught TypeError: Object #<Document>  has no method 'write'
>
> >> ... this occurs on the following statement:
>
> >> $doc.write($intern_64);
>
> >> ... where $intern_64 is set to "<script
> >> defer="defer">discusswrite.onInjectionDone('discusswrite')</script>"
>
> >> 2. Uncaught TypeError: Cannot set property 'cssText' of null
>
> >> ... this occurs on the following statement:
>
> >> iframe.style.cssText = $intern_37;
>
> >> It seems that the iframe.style is null at that point.
>
> >> I'm flummoxed as to the reason for these error messages. If I turn the
> >> page into a status HTML page - my app won't work properly in this
> >> fashion, but just for the sake of testing - then everything works just
> >> fine. Can you help me understand what's going on here, and how I might
> >> get around it?

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.