George
June 25, 2024, 4:17pm
8
First the config.js is not a critical file, it is used only by Wappler UI for meta data pop-ups.
Second the issue is because of a bug in Electron that is already open for 7 months and the Electron team haven’t fixed yet.
See:
opened 03:45PM - 23 Nov 23 UTC
bug
component/node-integration
platform/all
status/confirmed
has-repro-gist
26-x-y
27-x-y
28-x-y
### Preflight Checklist
- [X] I have read the [Contributing Guidelines](https:/… /github.com/electron/electron/blob/main/CONTRIBUTING.md) for this project.
- [X] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/main/CODE_OF_CONDUCT.md) that this project adheres to.
- [X] I have searched the [issue tracker](https://www.github.com/electron/electron/issues) for a bug report that matches the one I want to file, without success.
### Electron Version
27.1.2
### What operating system are you using?
Windows
### Operating System Version
Windows 11 Pro 22H2
### What arch are you using?
x64
### Last Known Working Electron version
_No response_
### Expected Behavior
Removing an iframe after closing a file watcher should not throw any errors.
### Actual Behavior
When you close a file watcher just before removing an iframe you see 2 or 3 Uncaught illegal access errors in the console. A workaround is to do the iframe removal first and then close the file watcher.
### Testcase Gist URL
https://gist.github.com/dmx-patrick/a176609a8664c2e98599b710545c8997
### Additional Information
_No response_
We hope to rewrite the usage of this file in the next major Wappler version and we will be using much newer Electron so it might get fixed there as well.
1 Like