topic Re: Custom Loading Indicator for WebFrame + Event Router Boolean Handling in ThingWorx in ThingWorx Developers

Custom Loading Indicator for WebFrame + Event Router Boolean Handling in ThingWorx

PG_14395514 — Wed, 18 Mar 2026 06:13:19 GMT

Hello Everyone,

I am working with the WebFrame widget in a ThingWorx Mashup and facing an issue related to loading indication.

When the URL inside the WebFrame takes time to load, there is no built-in loading indicator or event to detect the loading state. I want to display a custom loading indicator (spinner) until the URL is fully loaded.

My requirements:

Show a custom loader when WebFrame URL starts loading
Hide the loader once the URL is completely loaded

Challenges:

WebFrame does not provide any loading status or onLoad event
I cannot reliably detect when the content has finished loading

Additional Issue (Event Router):
I tried using the Event Router to control a BOOLEAN variable (e.g., isLoading) for showing/hiding the loader. However, I am not sure how to properly pass or assign TRUE/FALSE values through the Event Router.

Questions:

Is there any way to detect WebFrame loading start/end events in ThingWorx?
What is the best practice to implement a custom loading indicator for WebFrame?
How can I correctly use Event Router to assign TRUE/FALSE values to control loader visibility?

Re: Custom Loading Indicator for WebFrame + Event Router Boolean Handling in ThingWorx

MA8731174 — Wed, 18 Mar 2026 06:18:13 GMT

Hi @PG_14395514 which type of file are you loading on WebFrame widget? If its just a pdf file or some other types of files are also included?

Re: Custom Loading Indicator for WebFrame + Event Router Boolean Handling in ThingWorx

PG_14395514 — Wed, 18 Mar 2026 06:25:16 GMT

The WebFrame is currently loading dynamic URL. The load time varies depending on the content.

My main goal is to show a custom loader/spinner while the content is loading and hide it once rendering is complete. Since WebFrame does not expose any loading events, I’m trying to explore possible workarounds.

Please let me know if the behavior differs based on content type and whether there are any recommended approaches for handling loading states in such cases.