Wt

It even seems to be easier to reproduce than I thought. All you need to do is right click a link and say open in new tab. This new tab will have have links in it with the ?wtd=..., and the url will break. If you then reload that tab things work properly.

(Tested with iceweasel 22.0)

Kurt Roeckx wrote:

It even seems to be easier to reproduce than I thought. All you need to do is right click a link and say open in new tab. This new tab will have have links in it with the ?wtd=..., and the url will break. If you then reload that tab things work properly.

I don't see this with a current git snapshot anymore. Instead some of the sessions appear to be dead. Clicking on links (WAchor) doesn't do anything in some of the tabs, neither does a WPushButton. I seem to be able to reproduce this in about 50% of the times I try this.

I can't reproduce this on the webtoolkit.eu website, but I can reproduce the old behavior there.

I can only reproduce the last behavior when I have progressive-bootstrap set to true in wt_config.xml. When it's set to false things seem to work as expected so far.

And now I can't reproduce it at all anymore.

And this morning I could reproduce it again with bootstrap set to true.

It seems that after a restart things work normally for a while, but after some time something gets broken

One thing I noticed today was that on the tabs that didn't work the image also wasn't loaded.

So I've been running with progressive-bootstraps set to false for a few days now without any problems, so it seems to me that it's related to the progressive bootstrap that for some reason doesn't finish.

One other thing I notice that when the progressive bootstrap is turned on is that the number of sessions that are really open seems to be wrong, I think it keeps sessions around that should have been closed. I didn't see that behavior when progressive-bootstrap was set to false.

Which part can't you reproduce?

Can you reproduce this original issue that I still see with webtoolkit.eu? I can reproduce this 100% of the time.

So I just tried this with chromium instead of iceweasel (firefox), and I couldn't reproduce it.

So I then tried it with iceweasel on a different PC, tried to disable all of the extensions and I keep reproducing it. I created a new profile. I keep reproducing this all the time.

I also tried this on a windows PC with a real firefox. It still had 15 installed, I couldn't reproduce the behavior with that version. Then I upgraded it to 26 and I could reproduce the behavior.

So I have to come to the conclusion that either firefox broke something between version 15 and 22, or that Wt does something wrong that the new version of firefox triggers.

Kurt

Hi Kurt,

I can reproduce your issue on www.webtoolkit.eu. I believe the issue you see on webtoolkit.eu was solved in august. I don't know where our release of the wt homepage went wrong, but it looks like webtoolkit.eu is running an old minified version of Boot.js. The boot.min.js in the wt 3.3.1 release looks fine.

Thank you for reporting this, we'll update webtoolkit.eu.

Best regards,

Wim.

So like I said, I also saw that first issue as being solved for me with the current git version. However I'm still seeing issues with the progressive bootstrap but they're harder to reproduce. One day it's 50% of the time, the other it works without problems.

I still think that not cleaning up the session is related because I think the bootstrap never finished, the page isn't completely rendered.

Kurt,

Do you see any errors in the JavaScript console when this happens? An unexpected JS exception may cause this, but I failed to reproduce this on my computer.

BR,

Wim.

I've tried with both the build in web console and with firebug, but neither wants to debug what I open in a new tab for some reason.

Can we reproduce the problem on a public URL? (you can mail me if you don't want to make it overly public)

Wim.