## Description

In Chromium (native Wayland), clicking the **profile avatar** button in the toolbar fails to open the profile bubble. Instead of the full panel, only a clipped, near-zero-height black sliver is drawn near the anchor point.

The trigger is the **logical width of the Chromium window**, not the display itself. The same external monitor works fine when the window is narrow, and breaks when it is maximized.

Screenshot of the broken state is attached below.

## Steps to reproduce

1. Attach an external 4K display (3840x2160).
2. Move Chromium to the external display and maximize it (logical width ≳ 2500px).
3. Click the profile avatar button at the right of the toolbar.
4. The profile bubble renders as a thin clipped sliver instead of the full panel.

## Expected

The profile bubble opens fully, as it does on the internal display.

## Actual

A ~2px-tall clipped black rectangle is drawn near the avatar; the panel content is not visible or interactive.

## What I tested

I varied the external monitor scale to change the window's logical size, keeping everything else constant:

| Display / config | Logical window size | Result |
|---|---|---|
| eDP-1 (internal), scale 2 | ~1896x1030 | works |
| HDMI-A-1 (external), scale 2 | ~1896x1030 | works |
| HDMI-A-1, scale 1.5, half-screen | ~1250x1390 | works |
| HDMI-A-1, scale 1.5, maximized | 2536x1390 | **broken** |
| HDMI-A-1, scale 1, maximized | ~3820x2100 | **broken** |

So it breaks somewhere between ~1920 and ~2536 logical window width. I did not narrow the threshold further.

## Ruled out

- **Fractional scaling** — the external display also breaks at integer `scale = 1`, so a fractional scale is not the trigger.
- **Omarchy's global `GDK_SCALE=2`** (set in `hypr/monitors.lua`) — a fresh Chromium launched with `env -u GDK_SCALE` and a throwaway `--user-data-dir` reproduces the bug identically on the external display.
- **Omarchy's Chromium window rules** — `default/hypr/apps/browser.lua` only applies an opacity/tile tag, which applies at every window size, including the sizes that work.
- **XWayland** — `hyprctl clients` reports `xwayland: false`; this is native Wayland.
- `hyprctl configerrors` is clean.

## Note on ownership

This may well be an upstream Chromium (Ozone/Wayland `xdg_popup`) or Hyprland positioner bug rather than an Omarchy bug — I could not find anything Omarchy-specific that causes it. Filing here since Omarchy ships the Chromium defaults and the `scale = "auto"` monitor config that produce this out of the box on a 4K external display. Happy to move it upstream if that's the right call.

## System details

- **Omarchy:** 4.0.0-1
- **Hyprland:** 0.56.2 (commit efb5099, 2026-08-05)
- **Chromium:** 151.0.7922.173 (Arch Linux), native Wayland
- **Kernel:** 7.1.8-arch1-3
- **CPU:** Intel Core i7-1165G7 (Tiger Lake)
- **GPU:** Intel TigerLake-LP GT2 [Iris Xe], `i915`
- **Machine:** Lenovo ThinkPad X1 Carbon Gen 9 (20XW006HPB)
- **Monitors:**
  - `eDP-1` — 3840x2400@60, scale 2
  - `HDMI-A-1` — LG ULTRAFINE, 3840x2160@60, scale 1.5 (from `scale = "auto"`)

Chromium flags in use (`~/.config/chromium-flags.conf`, Omarchy default):

```
--ozone-platform=wayland
--ozone-platform-hint=wayland
--password-store=gnome-libsecret
--enable-features=TouchpadOverscrollHistoryNavigation
--load-extension=/usr/share/omarchy/default/chromium/extensions/copy-url,/usr/share/omarchy/default/chromium/extensions/yt-dlp,/usr/share/omarchy/default/chromium/extensions/whatsapp-slim
```