You are not logged in.

Dear visitor, welcome to 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.


Saturday, May 14th 2022, 2:08am

select menu not opening on android mobile in krpano plugin interface


We have a custom interface using KRPANO and we are running into the issue where on a HTML <select> menu we are not able to open it on Android Mobile.

Has anyone ran into this issue?

Thanks for any help!

Michael *g*


Friday, June 10th 2022, 11:29pm

Are bumps allowed?

If not please disregard my bump.


Wednesday, August 9th 2023, 7:18pm

If not please disregard my bump.
Same too u. Is it solved yet?


Thursday, August 10th 2023, 4:58pm


do you have a link to your example or a test-case?

If custom interface html code was added via the textfield - is the interactive setting enabled:

Best regards,


Thursday, August 10th 2023, 5:59pm

You can test it here. Click on ruler icon then you can see a select option unit on the right top of the page
I'm using html in data element and then add it using addlayer method type "text"

This post has been edited 1 times, last edit by "jack bauer" (Aug 22nd 2023, 6:09am)


Thursday, August 10th 2023, 6:16pm

As first step please try adding: interactive="true"


Thursday, August 10th 2023, 6:39pm

As first step please try adding: interactive="true"
It's not working :(


Thursday, August 10th 2023, 10:34pm

I was able to reproduce this now - but it seems like a Chrome bug...

When using html-form-elements like <select> or <input> inside another html-element that listens to touch events (like a krpano <layer> element does), then these form-elements don't work anymore... even when nothing will be done with the touch-events...

But after some trying I've found a workaround - when there are touch-events inside a layer on 'form-elements', then these touch-events on them will be captured and canceled and instead artificial mouse-events will be sent to the form-elements. And with these 'mouse'- instead of 'touch'-events the form-elements are working as expected.

That workaround will be included in the next krpano release.

Best regards,