Shelley Vohr

@markh-discord this issue was originally opened in 2017 - are you referring to a new different behavior?

@nkallen can you expand on > PLUS there is some very strange/incorrect queueing behavior introduced in Electron 29

@dsanders11 done!

Unfortunately it looks like something changed upstream - on our end we call https://github.com/electron/electron/blob/f595443a22a01b61750942532cbf38bef12626f3/shell/browser/api/electron_api_screen.cc#L88 which hasn't changed in years and ends up falling down to [`ui/ozone/platform/wayland/host/wayland_screen.cc;l=339-360`](https://source.chromium.org/chromium/chromium/src/+/main:ui/ozone/platform/wayland/host/wayland_screen.cc;l=339-360;drc=1f1840e1edf23b87e52d66ce18c36f845df182c0;bpv=1;bpt=1) and [`ui/ozone/platform/x11/x11_screen_ozone.cc;l=143-147`](https://source.chromium.org/chromium/chromium/src/+/main:ui/ozone/platform/x11/x11_screen_ozone.cc;l=143-147;drc=1f1840e1edf23b87e52d66ce18c36f845df182c0;bpv=1;bpt=1) respectively. I...

I opened a CL: https://chromium-review.googlesource.com/c/chromium/src/+/6563806

Happened again [here](https://github.com/electron/electron/actions/runs/15238114060/job/42873628646?pr=47255) - test is most likely [this one](https://github.com/electron/electron/blob/3212f60d690dc143037dd4a76a618b605f7c2d3d/spec/api-web-contents-spec.ts#L2800-L2816)

@ckerr it needs some tweaking but i still want to land it!

@hopejr no, but i'm working on it via https://github.com/electron/electron/issues/46924

Closed via https://github.com/electron/electron/pull/46353 - See https://github.com/electron/electron/issues/46924 for progress on windows.

@tzahola Electron has a [patch policy](https://github.com/electron/electron/blob/43dbd1bdf8a48d798f4e392f921bde81a3430f4b/docs/development/patches.md). Whether or not the new patch removes the need for the non-patch similar solution does not address the issue at hand, which is that...