If the problem resides on the KRpano side, you could try and call the updatescreen() function or even more extreme (i think) the updateobject(true,true) function on onloaded. If this corrects the problem, it means that somewhere some attribute,variable,thing is being cached that influences some setting after KRpano is finished setting up the object.

A quick and dirty method to check if the caching problem is to force the XML not to be cashed. There are several options to do something along these lines. By using meta in the HTML file to adding a random variable to the URL of the XML.

These should only be a temporary measures to check where the problem lies. But it seems to me that the anomaly could just as well be the second loading of the object, not the initial one.

I know this bug and it seems to come back every now and then with a new krpano-release (or maybe it´s a browser-issue). For me the problem is the height of the textfield, which seems to not get calculated correctly the first time. My workaround is to set autosize to none and the height after the plugin is loaded....

autosize="none"
onloaded="set(height,30)"