Klaus, You're the best. The for in loop that I thought was in krpano 1.19 pre-release was actually in a different minified third party js library. I tested again and took a closer look and you are correct, the bug is fixed in the latest version. Thank you for the quick response! Adam

I've run across a possible bug in the HTML5 krpano viewer version 1.17.4 (branding free) and it appears the same bug also exists in krpano 1.19 pre-release. I'll try to give as much detail as I can to reproduce the bug. The bug in krpano is revealed by a third party javascript library that adds methods to the Array.prototype. The third party code does something like this: Quellcode 1 Array.prototype.contains = function() {} Although manipulating the Array prototype is generally considered a bad ...

Nevermind... I'm a newbie and discovered that the buttons are in our code. The html overlay could indeed be the issue. I'll keep digging.

More info: The only button that responds is the full screen button and it just disappears. The rest of the buttons show the animation of being pressed, but do nothing.

I'm looking into this issue also and it doesn't appear to be an html element layered over the krpano viewer (I could be wrong, I haven't completely ruled it out yet). The one reason I think that it isn't an html element layered over the viewer is that the krpano buttons are still touchable. However, the button events don't fire when on android. It works in iOS and from a desktop browser. It could be something specific with the Android browser and the touchstart / touchend events.