After updating to version 1.21, the order of overlapping text and blurring is different.

Hello,

When we updated our built VR tour to version 1.21, we encountered a problem that was not present in the previous version.

I am using pp_blur.js to blur panoramic images, hotspots and text in the opening.
After updating to version 1.21, the blurring process is no longer applied to text only.

We also verified the relevant text in the Developer Tools and found that the div elements surrounding the text were output dynamically and the z-index value was automatically set to 2000~.
In previous versions (1.20.10) such a div element did not exist.

The text is an arrow annotation to transition to the next scene, and it's read from the scene gallery title.
Note that this process is performed only in the SP screen.

Below is the source code.

pp_blur.js loading

<plugin name="blur" keep="true" if="skipintro != true"
	url="../plugins/pp_blur.js"
	range="30" quality="7" phase="2"
	onloaded="tween(layer[introscreen].bgalpha, 0.33, 3.0);"
/>

Text Styles

<style name="hogehoge" type="text" enabled="true" vr="true"
	rx="0" ry="0" rz="0" edge="top"
	css="font-family:Arial; font-size:14px; color:#fff;text-align: center;"
	txtshadow="0 1 8 0x000000 1.0"
	bg="false"
	
/>

Annotation text display

<action name="get_sp_ann_text" scope="local" args="anntype">
		calc(sp_name, caller.name + '-sp');
		if(anntype == 'arrow',
			calc(hs_title, scene[get(caller.linkedscene)].title);
		,anntype == 'wave',
			calc(hs_title, caller.tooltip);
		);
		calc(hs_ath, caller.ath + 0.0);
		calc(hs_atv, caller.atv + 15.0);
		addhotspot(get(sp_name));
		hotspot[get(sp_name)].loadstyle(hogehoge);
		set(hotspot[get(sp_name)],
			html=get(hs_title),
			ath=get(hs_ath),
			atv=get(hs_atv),
		);
		if(anntype == 'wave',
			set(hotspot[get(sp_name)].vrstatus, true); set(caller.vrstatus, true);
			if(webvr.isenabled,
				set(hotspot[get(sp_name)].visible, false);
			);
		);
	</action>

⇩Ver.1.20.10

⇩Ver.1.21

Hi, Klaus

Quote from klaus.krpano

that's because textfield hotspots are rendered using CSS 3D-transforms instead of WebGL by default now in version 1.21 (for performance reasons).

Please see here in the Release Notes under Compatibility Notes / Important Changes the note about renderer="auto".

I see that it was mentioned in the release notes. My lack of research...
I will check again.

Quote from klaus.krpano

That means to 'fix' it, add renderer="webgl" to your hotspot (or the style that got applied to the hotspot).

I was able to fix it successfully by adding renderer="webgl" to the style I am applying to the text! Perfect!

Many thanks,
Klaus