Shelley Vohr
Shelley Vohr
@StaZhu rebasing should fix the error
@bpasero sure, i think that's possible here! I can rework this to allow for a bit more control.
@bpasero tweaked it a bit to allow disabling border or setting to a custom color.
@bpasero hmm, do you have a sample? Running the following: ```js const { app, BrowserWindow } = require('electron') const path = require('node:path') function createWindow () { const mainWindow = new...
@bpasero could you please open a follow-up issue for updating the color after the window is created?
Tracked to https://chromium.googlesource.com/chromium/src/+log/123.0.6296.0..123.0.6312.5?n=10000&pretty=full
Hey folks - I've determined this is unfortunately part of Chrome Refresh 2023. We inherited it in https://chromium-review.googlesource.com/c/chromium/src/+/5247338, when they enabled the flag by default (and then later removed it...
As a follow-up to the above - there's nothing we can do on our end about this short of reverting it and we're not going to diverge from Chromium in...
Could you please attach a crash dump to help us get more information? You can collect them by adding the following snippet to your main process code, before `app.whenReady`: ```js...
Thanks for the update - in that case we'll work on some documentation to potentially highlight this. If you move Google Chrome to the D Drive, do you also experience...