You are not logged in.

Dear visitor, welcome to krpano.com Forum. If this is your first visit here, please read the Help. It explains in detail how this page works. To use all features of this page, you should consider registering. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

  • "sachagriffin" started this thread

Posts: 1,850

Occupation: Virtual Tours - Photography - Krpano developer

  • Send private message

1

Monday, September 10th 2012, 9:41pm

Blocking element on html5 viewer

I upgraded to the latest version, and something is blocking user interaction.. on the ipad its the whole screen and desktop safari it's the left side.

I assume this is something related to text fields, but I removeplugin(everything) and it still exists.

This is the blocking html
<div style="height: 100%; font-size: 12px; font-family: Times; position: absolute; left: 0px; top: 0px; width: 1000px; "><div style=""><div style="margin:2px 2px 2px 2px;"></div></div></div>

will continue digging....

related to
<plugin name="text_desc" url="%SWFPATH%/plugins/textfield.swf" html="" x="140" y="20" width="1000" autoheight="true" selectable="false" background="false" borderwidth="0" align="lefttop" zorder="2" enabled="false" keep="true" alpha="0" visible="true" tag="nav" />

interesting to note that this is enabled="false" and removeplugin has no effect.
Removed the offending plugin, perhaps autoheight fails with no html specified.
YUP, this is exactly what the problem is.
KRPano Developer: Portfolio ::Gigapixel Tagging Solutions - Porfolio 2 :: Facebook :: Twitter :: reddit.com/r/VirtualTour

This post has been edited 3 times, last edit by "sachagriffin" (Sep 10th 2012, 10:02pm)


2

Tuesday, September 11th 2012, 3:13pm

Hi,
perhaps autoheight fails with no html specified.
right, that's the problem!
there is no special check if the 'html' setting is empty, and so the 'waiting' for the browser to get a height greater than 0 will fail and a 'buggy' html element was left on the page...

that will be fixed in the next release,

best regards,
Klaus