calling a backend function onload results in an uncaught referenceerror about webui HOT 7 CLOSED

Are you referring to the error that the websocket is not connected yet?

from webui.

ws needs to wait for the connection, and executing it immediately or onload will cause an error
Maybe the later js library can add an event queue and execute it after the ws connection is established.
@hassandraga

from webui.

Sorry - two different errors - yes, with window.onload i'm getting websocket is not connected and with the script at the end of the html doc i'm getting uncaught referenceerror: <function_name> is not defined.

I'm trying to populate the html page with data from a local sqlite database when the app starts - it would be nice if that could happen as quickly as possible - thanks -

from webui.

The second mistake you meet is "Uncaught ReferenceError: webui is not defined at...." right?

This is related to the rendering process of the browser. By default, the inline script in HTML will be executed immediately after the HTML is loaded, but webui.js has not been executed yet, which results in the webui variable not being available in the global scope.

from webui.

you can use defer for <script>, note that this is only valid for external js files, and the execution order of these js files maintains their relative order, just like a regular script

from webui.

This is fixed in a commit, it's available in the nightly build.
More info in this discussion.

document.addEventListener('DOMContentLoaded', function() {
	// DOM is loaded, and `webui` object should be available.
	webui.setEventCallback((e) => {
		if (e == webui.event.CONNECTED) {
			// Connection to the backend is established
			console.log('Connected.');
		} else if (e == webui.event.DISCONNECTED) {
			// Connection to the backend is lost
			console.log('Disconnected.');
		}
	});
});

from webui.

@jinzhongjia - if using webui.call then yes, webui is not defined -- i was using the function name. i see now that webui isn't loaded until DOMContentLoaded so this all makes sense. i guess there is no way to establish the bridge before before the page/body is loaded...

@AlbertShown - thanks -- i'll check that out. I guess your event listener must fire right after the one referenced above -

from webui.