Window Management API not fully working on Opera GX
-
burnout426 Volunteer last edited by
@andremartinsc said in Window Management API not fully working on Opera GX:
However, when trying to open a new window on a specific screen using the left / top coordinates, the browser ignores those placement parameters.
Do you have a test case?
-
andremartinsc last edited by
@burnout426 The MDN demo (see below) is enough to reproduce the problem. If you try to open a popup on a secondary screen, Opera doesn’t respect the left/top coordinates — the window always ends up on the primary display. The dimensions (width/height) are applied correctly, so it looks like the API is partially implemented, but the multi-screen placement part just isn’t supported in Opera right now.
-
burnout426 Volunteer last edited by burnout426
@andremartinsc Okay. I can confirm the issue in Opera GX 121.0.5600.81 64-bit based on Chromium 137 on Windows 11 23H2. But, it works fine in Opera One 122.0.5643.24 64-bit based on Chromium 138.
Primary Screen: 1366 x 768
Secondary Screen: 1920 x 1080
Multi-monitor mode: ExtendIn Opera GX, on screen 0, I hover the "Popup" button and choose screen 1. The window opens on screen 0 instead. In Opera One, it opens on screen 1.
In Opera GX, on screen 0, I set "left" to 1500, and click the "window" button and it opens on screen 0. In Opera One, it opens on screen 1 because 1500 is greater than the width of screen 0.
-
andremartinsc last edited by
@burnout426 Thanks a lot for confirming and testing across both versions. Since it works fine in Opera One but not in GX, it does look like a GX-specific behavior (is this a bug or on purpose?).
I filed a bug report with the Opera GX team, but is there something else you’d recommend me doing?
-
burnout426 Volunteer last edited by
@andremartinsc I’m pretty sure it’s not intentional and I am going to guess it’ll be fixed automatically when GX moves to 138. So, we probably just have to wait. However, what’s the number for the bug you filed?
-
andremartinsc last edited by
@burnout426 I am not sure where I can find that information. I just filled the form.
-
burnout426 Volunteer last edited by
@andremartinsc It usually shows the number after you file and I think you get an email too. Things could have changed though. No worries.
-
andremartinsc last edited by
@burnout426 Found a JIRA link on the email I got.
https://opera.atlassian.net/servicedesk/customer/portal/118/GX-11124?token=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJ0Z3QiOiJhbm9ueW1vdXMtbGluayIsInFzaCI6ImRlNDlhNjkwMTEwY2E2MWFmZTFlZGNiMDM0NDJlYTVkODc0MWVhYWY2ZjU4M2E0ODcxOGFiYTBlYzRlMmI5YjgiLCJpc3MiOiJzZXJ2aWNlZGVzay1qd3QtdG9rZW4taXNzdWVyIiwiY29udGV4dCI6eyJ1c2VyIjoiMzM0Mjg3IiwiaXNzdWUiOiJHWC0xMTEyNCJ9LCJleHAiOjE3NjA0ODY5NTEsImlhdCI6MTc1ODA2Nzc1MX0.JI9wD0rT9kRILrU6E2fjz3tWebLMptWm0tTgxGe4gG4Are you 100% this is something they would fix on the next version? Is filing the bug enough or should I do anything else other than waiting?
-
-
leocg Moderator Volunteer last edited by
@andremartinsc We don't know if it will be fixed in the next version, but they will fix the issue at some point.
Usually reporting the issue is enough
-
burnout426 Volunteer last edited by
@andremartinsc I was just thinking it's a Chromium issue with Chromium 137. However, I tested in Chromium 137.0.7151.0, which is the closest compiled Win64 build I can find to 137.0.7151.122 that Opera GX uses. I also tested in Chromium 137.0.7152.0. Both of those builds work fine. No issues. So, it's less likely than I originally thought that it's just a Chromium issue. Still possible though.
Either way, those that need to know have been notified of your bug and this thread. Nothing more you can do at the moment.
-
burnout426 Volunteer last edited by
Any difference in Opera GX 122.0.5643.52 based on Chromium 138 that just came out?
