Andreas,
sadly I have to say that your page still has errors, the very fierst
error I get if I clean ally my
browser chache and than go to http://www.fsbutiken.se/ is:
Could not load 'tapestry.form'; last tried '__package__.is'
BUT: We have a caching proxy to connect to the internet!
If I disable the caching proxy, your site works without JavaScript
errors!
This at least gives some hints where the problem is.
Sadly we are no IE experts, has anyone a hint what we can do to make
Tapestry 4.1.1 / dojo / IE work with caching? Cause we can not control
if customers
have a chahing proxy or not...
Thanks, Max
>
> Maximilian,
>
> > Now we fond another posting
> > http://www.nabble.com/Why-is-IE6-freezing--tf3377078.html#a9399366
> > that reports the excat same problem, but the solution given
> seems not
> > to work for us.
>
> You referred to my posting. Here are comments on quotes of it:
>
> On 20 mar 2007, at 18.30, baleksandar wrote:
> > we have almost the same problem (msie freezing, javascript
> errors) by
> > using tomcat + tapestry 4.1 + MSIE.
> >
> > we hope maybe you could give us some hints how to solve this issue
> > especially because i see that your web page
> http://www.fsbutiken.se
> > doesn't work 100% well on msie, and i thought you are still
> working on
> > the fix? did you already realize that your page sometimes returns
> > javascript errors?
>
> Not sure if you're talking about an older version of the site.
> Anyway, I would
> be surprised to see that http://www.fsbutiken.se still does
> not work or give js errors. I tested and found no problems anymore.
>
> Keep in mind that it is *absolutely* necessary to empty the
> browser cache in IE *every time* you test. Otherwise you're
> hunting ghost problems...
>
> > Unfortunatelly, the solution you mentioned earlier doesn't
> work for as
> > - our server had all the time the compression flag turned off. the
> > question is does it really work for you?
> > we've tested our application using at least three client computers
> > with same configured msie browsers. Sometimes (but not
> always) we got
> > the javascript errors such "tapestry.form" object doesn't
> exist or the
> > msie just start to freeze. These errors always appear in
> conjunction
> > with use of tapestry SubmitLink component. we can not reproduce
> > that...
>
> The important part here is that something is that errors like
>
> > Could not load 'dojo.looging.Logger'; last tried '__package__.is'
> > Could not load 'tapestry.form'; last tried '__package__.is'
> > Could not load 'tapestry.form'; last tried '__package__.is'
>
> most certainly are related to either a serving problem or a
> js script error that prevents loading (I would bet it's not a
> script error).
>
> So double+triple check your tomcat configuration. Also make
> sure you don't do any special stuff in your border component
> or in your @Shell configuration.
>
> Andreas Pardeike
>
> PS: I would really love to see some error checking on this.
> It's really hard to catch any errors resulting from asset
> linking problems.
>
> --
>
> On 21 mar 2007, at 19.43, Jesse Kuhnert wrote:
>
> > IE is a little less forgiving with javascript errors, so if you get
> > one all other code will be skipped. (a lot of the time)
> >
> > I fixed what was a very subtle IE specific bug recently in
> > 4.1.2-SNAPSHOT. You may try that "just to see" . ...I only have IE7
> > available to me right now, but should be able to get a hold of my
> > vmware ie6 image tomorrow and take a look at what is
> happening after
> > that.
> >
> > Have you noticed any errors happening before "not able to load
> > package" things?
> >
> > On 3/21/07, Maximilian Wei?bock <[EMAIL PROTECTED]>
> > wrote:
> >> We have a very hard problem with a Tapestry 4.1.1 Application on
> >> Windows IE 6.
> >> We get javascript errors all the time (even if they are not
> >> reproducable on all developer machines) using IE 6.
> >>
> >> Some of the errors are:
> >>
> >> Could not load 'dojo.looging.Logger'; last tried '__package__.is'
> >> Could not load 'tapestry.form'; last tried '__package__.is'
> >> Could not load 'tapestry.form'; last tried '__package__.is'
> >>
> >> On a german IE we get more or le
