I am witnessing the sporadic failure of TextFields to render properly in the HTML5 viewer. I am using the latest 1.16.3 version and am testing using OS X Mountain Loin, with up-to-date versions of Chrome, Firefox, and Safari. The sporadic failures are taking place in testing on all three browsers.
When they fail, the TextFields do not use the width property that is defined for them - they instead use the default width of 400px. All of the textFields defined in my XML have explicit withs defined on them, i.e.
<hotspot style="infotext" autoheight="true" align="leftbottom" edge="leftbottom" width="90" html="Apollo Temple" atv="3.2950" ath="-77.567" />
The "infotext" style is defined as follows:
<style name="infotext"
url="textfield.swf"
visible="false"
children="false"
css="text-align:center; color:#FFFFFF; font-family:Arial"
autoheight="true"
vcenter="false"
background="true"
backgroundcolor="0x000000"
backgroundalpha="0.4"
border="true"
bordercolor="0xFFFFFF"
borderalpha="1.0"
borderwidth="1.0"
roundedge="0"
shadow="3.0"
shadowrange="4.0"
shadowangle="45"
shadowcolor="0x000000"
shadowalpha="1.0"
textshadow="0.0"
textshadowrange="4.0"
textshadowangle="45"
textshadowcolor="0x000000"
textshadowalpha="1.0"
onautosized=""
handcursor="false"
/>
The failures seem to be quite haphazard - the panos render properly about 90 percent of the time. And the failures do not seem to be associated with particular panoramas - sometimes a particular panorama will render correctly, sometimes not. When the failure does take place, it usually is only for a portion of the TextFields within the panorama, with all the incorrectly rendered TextFields in a continuous pan range with no intermingled correctly rendered TextFields. Note that the TextFields are not defined in order by pan in the xml file, so I don't think the set of TextFields that fail is associated with their order in the xml file.
I have attached a screen shot of what the failure looks like.
So is anyone else seeing this, and maybe have a workaround? Any hope for a fix, Klaus? It really, really smells like some kind of race condition, but tracing within my code did not provide any insights, so I have to suspect that it is deeper within the KRPano code itself.
Cheers,
Larry Wieland