Electron Releases

Description of Change

dialog.showOpenDialog() / showSaveDialog() (and the download manager's default Save prompt) run the native dialog on dialog_thread, and ShowFileDialog resolved the parent HWND there via NativeWindowViews::GetAcceleratedWidget() → views::Widget::GetNativeWindow(), which reads a UI-thread WeakPtr. In DCHECK builds that's sequence_checker.cc: CalledOnValidSequence and a browser-process crash (CI hit); in release builds it's an unsynchronised read of a window the UI thread may be tearing down.

• Resolve the HWND on the UI thread in ShowOpenDialog/ShowSaveDialog/Show*DialogSync and pass it into the dialog-thread function, the same way message_box_win.cc has done since the M110 roll. No header or cross-platform change.
• The CI hit came from asar-spec.ts "saves a packed PDF from the PDF viewer": its click loop can start a second download, which had no will-download handler and fell through to the real Save dialog. Give every download from that test a save path (or refuse it) synchronously in will-download.

Checklist

• PR description included
• npm test passes

Release Notes

Notes: Fixed a possible crash on Windows when a file dialog was shown for a window that was being closed at the same time.