Bug report: HTML content disappearing from hotspots

zbooy · April 6, 2023 at 7:34 PM

Hi,

on my website the 03-30 update causes the HTML content of child text layers of a hotspot to magically disappear if they are far outside the starting viewport. The 02-09 version works fine.

It probably has something to do with the "pixel-exact visibility check for the flat/2d'-hotspots" mentioned in https://krpano.com/forum/wbb/inde…&threadID=19253. Funny thing is that it's only the HTML content that is gone, the background part is properly sized and visible! (See the attached pic.) When inspecting with the DevTools the innermost divs are no longer there.

kme · April 6, 2023 at 7:51 PM

i can confirm this happening. several reports from users when using the annotations.

kme · April 6, 2023 at 9:44 PM

Was able to put a simple example online where this bug can be simulated:

https://krpano.kri-soft.be/examples/htmlbug/

Replicate the bug:
- click the text "click me" top left while viewing hotspot 1
- turn to view hotspot 2
--> the text in the layer is not visible (layer is visible)

It does work when the layer is in viewing range:

- reload page
- turn to view hotspot 2
- click the text "click me" top left
--> the layer appears with text visible

gr,
Kristof

kme · April 7, 2023 at 9:15 AM

just tested on other devices"
- ipad chrome 107.0.5304.66: no issue
- android chrome 111.0: bug present
- pc chrome 112.0 - bug present

klaus.krpano · April 7, 2023 at 2:17 PM

Hi,

thanks for the text-case!
I'm already on it.

Hidden textfields are unfortunately bit tricky - krpano 1.21 has the new possibility to dynamic track text/html-content changes of textfields, but when a html element is 'invisible' to the browsers DOM (document object model) for some reason, the browser doesn't report any size anymore. In such cases the related text/html-element gets temporary moved into a 'DOM-visible' (but still invisible on screen) element, then waits for the size and when the source elements gets visible again, moved back. Additionally this depends on CSS3D vs. WebGL, dynamic changes, layer or hotspot, browser-differences, performance-optimizations and the WebXR API is also a special case.
So all in all a quite complex system with unfortunately many unexpected/hidden cases, but when finding them, everything is solvable of course ;-).

Best regards,
Klaus

s-maier · April 7, 2023 at 3:09 PM

Quote from klaus.krpano

So all in all a quite complex system with unfortunately many unexpected/hidden cases, but when finding them, everything is solvable of course ;-).
Best regards,
Klaus

And this is, what pre release versions are there for, right?

At least I have to say it is big fun for me to play with the PR versions. But not only that, also lurking the forum in the last weeks, seeing what others find and want and watching this being fixed or implemented is splendid fun

Participate now!