tight summit
I'm trying to use invoke from external url in webview with dev branch of tauri.
And it shows error in the console (attached image)
I can't use invoke on that website at all.
Steps to check it:
git clone https://github.com/tauri-apps/tauritauri.config.json in helloworld and remove default windowmain.rs of helloworld example with main.rs and run it, then open console
stable pebble
tracked here https://github.com/tauri-apps/tauri/issues/8476 - solution will probably mean we have to disable the new&faster ipc in favor of the old v1 one for external urls.
tight summit
tracked here <https://github.com/tauri-apps/tauri/issues/8476> - solution will p...
Disable (revert) or adding an option to select new / old ipc?
stable pebble
adding an option
switching every user/app back to the old ipc would be horrible lol
the option should be fairly easy to add because the old ipc is still in use on old linux versions where the new one can't be used
tight summit
tracked here <https://github.com/tauri-apps/tauri/issues/8476> - solution will p...
How about modifying csp on the fly / pre configure. eg. if I only need .google.com and ipc.local. then just modify it and allow it
stable pebble
the question is how you want to do that
the csp config in tauri.conf.json is basically an alias for the meta tag (https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP), nothing fancy
tight summit
the question is how you want to do that
I'm trying to find solution without modify tauri itself
tight summit
the question is how you want to do that
intercept requests and modify csp, if tauri supports
stable pebble
not possible
well, maybe with a proxy or something
but not with the webview apis themselves
at least if you need cross platform support
tight summit
not possible
Hmm. So I'll look into adding the option the WebviewBuilder to use old IPC.
You think it's worth a PR?
stable pebble
yes
cc @coral bridge
(or should that be handled automatically somehow? probably not worth and would probably cause more issues than it solves)
coral bridge
if you control the remote website you could still use the new IPC right?
then yes it should be an option on the builder
yikes
stable pebble
if you control the remote website you could still use the new IPC right?
yeah
tight summit
I just discovered that the older IPC is much slower and it's not recommend to use it
And I found that this issue already found in pull/7764
I think that there's a way to still use fetch and allowing calling the IPC with fetch by this:
developer.apple.com/nsallowsarbitraryloads
And
developer.apple.com/nsexceptiondomains
And adding this to info.plist
stable pebble
this is all completely irrelevant
except the part saying that the older ipc is slower and not recommended of course
tight summit
this is all completely irrelevant
I guess that I'm talking on window level where the problem is webview level