Niklas Wenzel
Niklas Wenzel
Electron v38 has been released. Did it fix this issue?
@michaelBelsanti Thanks for reporting back!
Thanks for opening an issue! Could you please upload your test code as a gist through [Electron Fiddle](https://www.electronjs.org/fiddle)? Could you please also describe in the issue itself what behavior you'd...
Not in a position to comment on the code, unfortunately. > Due to lack of development environment I choose drop Linux support for now. In the past, I've rented a...
Note: This should be optional to support use cases such as the following: - Delta updates (e.g., via Squirrel.Windows) - Staged rollouts (e.g., via Squirrel.Windows)
Thanks for reporting! I'm not sure if this is a Forge issue. I'd personally file it in the [main Electron repository](https://github.com/electron/electron/issues). However, before you open an issue there, please check...
For everyone trying to get Trusted Signing to work, you can look at https://www.electronforge.io/guides/code-signing/code-signing-windows#using-azure-trusted-signing for a working configuration.
I investigated the upstream Chromium issue today. See my [comment on the Chromium bug tracker](https://issues.chromium.org/issues/40811608#comment14). I managed to create a Chromium patch that fixed this behavior (not fully polished though,...
Thanks for the update! I still wouldn't mention it in the Forge docs because it's not an issue with Forge.
Reopening and marking as stale-exempt.