Chromium extension windows appear very narrow

[mrkajetanp]

I'm experiencing a strange issue with the windows created by chrome/chromium extensions. Whenever I try clicking on them they appear very narrow and not usable. I did not have the same issue with Gnome on Wayland and Chromium is running in Wayland mode. I'm not sure if it's directly related to this project but asking here in case someone has seen this before.. Screenshot below.

[vaxerski]

check on sway-git

[adwaymalhotra]

I face the same issue on Hyprland.

The extension windows are fine in chrome on sway.

[mrkajetanp]

Thanks for checking on sway, do you use normal chrome or some chromium variant?

[adwaymalhotra]

It's normal chrome. I initially suspected it may be a chrome issue but checked on sway after I saw this bug.

The issue has been there for at least a few months on Hyprland. Can't say if the issue existed on sway in the past.

[vaxerski]

would help if I could reproduce this

[mrkajetanp]

Interesting, are you running chrome in Wayland mode or through XWayland? Which version is it?

[vaxerski]

wayland, newest from arch repos, chromium

[adwaymalhotra]

Interestingly, it doesn't happen when the window is fullscreen using bind=SUPERALT,F,fullscreen,1 on the external monitor(s).

On the laptop screen, it happens every time: fullscreen or not.

[schmensch]

I'm having the same issue on Brave with ozone-platform-hint set to wayland in chrome://flags, but only when brave is maximised.

• GNOME 44.2.1
• NixOS unstable
• Brave 1.52.122 / based on Chromium 114.0

[networkException]

This is https://bugs.chromium.org/p/chromium/issues/detail?id=1282790

[schmensch]

Thanks!

[Vogete]

So this happened to me too, and I finally figured out a workaround for it. So it always happens to me when my leftmost monitor's position in hyprland is not starting at 0:0. As soon as I moved it to 0:0 and re-positioned all other monitors next to it (I used wdisplays for a quick fix, but I assume it works with hyprland config too), the extension popups appeared normal again. If I position it back to something more right on the plane, it becomes narrow again.

This might not be a proper fix, but at least it made my extensions usable again.

[InnovateInfinity87]

So this happened to me too, and I finally figured out a workaround for it. So it always happens to me when my leftmost monitor's position in hyprland is not starting at 0:0. As soon as I moved it to 0:0 and re-positioned all other monitors next to it (I used wdisplays for a quick fix, but I assume it works with hyprland config too), the extension popups appeared normal again. If I position it back to something more right on the plane, it becomes narrow again.

This might not be a proper fix, but at least it made my extensions usable again.

This is working! as far as there is a monitor active starting at x=0 then the extensions show correctly. Thank you very much!

[jbhardman]

Aha, that 0x0 thing fixed it for me. I didn't even realize. I had configured my monitors so that when I did plug in to my monitor, it was at 0x0 and my laptop screen started after it at 2560x0. But most of the time I'm not plugged in. Since hyprland just acted normal without the first monitor, I didn't even imagine that my config of 2560x0 was a problem.

Now to figure out how to set variable monitor setups based on what is present...

[Alxandr]

Aha, that 0x0 thing fixed it for me. I didn't even realize. I had configured my monitors so that when I did plug in to my monitor, it was at 0x0 and my laptop screen started after it at 2560x0. But most of the time I'm not plugged in. Since hyprland just acted normal without the first monitor, I didn't even imagine that my config of 2560x0 was a problem.

Now to figure out how to set variable monitor setups based on what is present...

Exact same thing I had. Do let me know if you find a good solution.

[Magicking]

This situation happens, I fixed it by setting 0x0 to the monitor eDP-1 (I obtained from hyperctl monitors) settings which previously was at 2160x0 (due to usage of a tool to adjust another screen)

I fixed the settings eDP-1 0x0 directly in .config/hypr/monitors.conf

[LucStr]

I can very consistently reproduce and fix the issue as described by @Magicking . It happens if the first monitor located at 0x0 is not connected and the eDP-1 monitor is located not at 0x0. @vaxerski can you also reproduce this?

[vaxerski]

sounds like that one qt bug back in the day. I very much doubt this is a hyprland issue.

[izmyname]

Is this still actual?

[LucStr]

I used to very consistently get this issue. I haven't changed my setup and just tried to recreate it based on my description and cannot anymore. Therefore I think this can be closed.

[schmensch]

The issue on the chromium bug tracker is fixed, thus I guess this issue is fixed as well.