Replies: 1 comment 1 reply
-
Like i said in the linked issue, this isn't necessarily bad, it should fall back to another api that's not bound to cors / access-control. This also differs per website as they configure the access control headers on their end so it's possible that only one window has the issue, assuming that they use different URLs! |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello community,
Before I file this as a bug let me first check if I'm doing something wrong...
My situation:
My problem:
The first windows can emit messages and listen to the Tauri backend, but the second window is not allowed to do this:
[Error] Fetch API cannot load ipc://localhost/plugin%3Aevent%7Clisten due to access control checks.
Is this a well-know issue? I did find this issue, but my context is a slightly different (one window works, the other does not).
Thanks in advance!
Beta Was this translation helpful? Give feedback.
All reactions