iFrame blank when displaing http://<ipaddress LMS server>:9000/material

[karsten13]

@stephanvdplas

mm has a simple internal cors proxy you could try.

So instead using the <original-url> in the iframe you could try http://localhost:8080/cors?url=<original-url>.

E.g. if your <original-url> is https://example.com try http://localhost:8080/cors?url=https://example.com

[karsten13]

ups, sam was quicker …

[stephanvdplas]

@sdetweil said in iFrame blank when displaing http://<ipaddress LMS server>:9000/material:

@stephanvdplas said in iFrame blank when displaing http://<ipaddress LMS server>:9000/material:

Set-Cookie header didn’t specify a “SameSite” attribute and was defaulted to “SameSite=Lax”

Ok, I don’t KNOW for certain, but our cors proxy might work there

change the url in the iframe config to

http://localhost:MM_PORT/cors?

the rest like this

// the url 
url=http://www.test.com/path?param1=value1 // example
// if there are headers, skip if not 
&sendheaders=header1:value1,header2:value2&expectedheaders=header1,header2

make sure quotes around the url string’’

It doesn’t work. Now there are no errors, but it only shows an empty frame.

In the Preview tab, it shows {{snackbar.msg}}
[24-09-18 22:33:38.8839] Slim::Utils::Misc::msg (1319) Warniing : [22:33:38.8838] “my” variable $mobile masks earlier declaration in same scope at (eval 5777) line 46.

This warning is also seen in the debug log of LMS server, also when I open the 192.168.3.8/material on a browser on a windows machine (where the site is loading correctly).

[stephanvdplas]

@stephanvdplas There is another thing:

In the preview tab of the content it shows: Failed to load response data: Connection is closed, can’t dispatch pending call to Network.getResponseBody

[sdetweil]

@stephanvdplas now I am out of my knowledge range.

@karsten13 maybe has more skill here…

[karsten13]

@sdetweil said in iFrame blank when displaing http://<ipaddress LMS server>:9000/material:

@karsten13 maybe has more skill here…

sorry, no. Maybe google has some findings.

[karsten13]

you could try adding

        electronOptions: {
                webPreferences: { webSecurity: false },
        },

in config.js

[stephanvdplas]

@karsten13 good option. I tried it (actually I placed the option directly in the electron.js script) but it doesn’t change the situation at all.

[karsten13]

@stephanvdplas

I can only guess without having the debug case …

You can google and try changing electronOptionsDefaults and/or electronSwitchesDefaults in js/electron.js if you find something …

[stephanvdplas]

@karsten13 I am quite sure about having the config right:

	let electronSwitchesDefaults = ["autoplay-policy", "no-user-gesture-required"];
	app.commandLine.appendSwitch(...new Set(electronSwitchesDefaults, config.electronSwitches));
	let electronOptionsDefaults = {
		width: electronSize.width,
		height: electronSize.height,
		icon: "mm2.png",
		x: 0,
		y: 0,
		darkTheme: true,
		webPreferences: {
			contextIsolation: true,
			nodeIntegration: false,
			zoomFactor: config.zoom,
			webSecurity: false
		},
		backgroundColor: "#000000"
	};

	// DEPRECATED: "kioskmode" backwards compatibility, to be removed
	// settings these options directly instead provides cleaner interface
	if (config.kioskmode) {
		electronOptionsDefaults.kiosk = true;
	} else {
		electronOptionsDefaults.show = false;
		electronOptionsDefaults.frame = false;
		electronOptionsDefaults.transparent = true;
		electronOptionsDefaults.hasShadow = false;
		electronOptionsDefaults.fullscreen = true;
	}

	const electronOptions = Object.assign({}, electronOptionsDefaults, config.electronOptions);

	// Create the browser window.
	mainWindow = new BrowserWindow(electronOptions);

So the webSecurity line is the only thing I added/changed.