# 1Password: unlock popup unusable on fractional scaling, and its window rule targets a non-resizable window

Omarchy ships 1Password integration (installer, `omarchy-launch-1password`,
`SUPER + SHIFT + SLASH`, and window rules), so this is an out-of-the-box
experience problem rather than a purely local one. Three related findings, one
user-facing and two small code issues.

**Environment:** Omarchy 4.0.2-1, Hyprland 0.56.2, 1Password 8.12.34-34,
display 3840x2160 @ **scale 1.6** (logical 2400x1350).

---

## 1. The browser-unlock popup is unusable at fractional scale (upstream bug, workaroundable here)

Unlocking 1Password from the browser extension opens a popup that maps at
402x371 logical px while its UI is laid out for ~643x594 CSS px (402x371 x 1.6,
the display scale). The password field is clipped.

This is a 1Password bug — it reproduces with **all** Omarchy window rules
removed, and the popup is size-pinned so no window rule can correct it. But
Omarchy can work around it downstream, which matters because Omarchy installs
and launches 1Password itself:

    /opt/1Password/1password --force-device-scale-factor=1

With that flag the window size is unchanged (still 402x371) but the layout
matches it and the popup is usable. Suggested places: `omarchy-launch-1password`
and the autostart entry written by `omarchy-install-service-1password`.

Trade-off worth weighing before adopting: at scale factor 1 the app renders at
1x and the compositor upscales, so text is softer than native. It may be worth
applying only when the monitor scale is fractional.

## 2. `apps/1password.lua` applies a size rule to a window that cannot be resized

`default/hypr/apps/1password.lua:1` tags every 1Password window
`floating-window`, which pulls in `size = { 875, 600 }` from
`default/hypr/apps/system.lua:4`. The browser-unlock popup is size-pinned by the
app, so the rule cannot hold — and it produces an intermittent visible flash:
in one of five captured opens the popup was born at 875x600 and snapped back to
402x371 within ~100ms. (`resizewindowpixel` on this window likewise returns `ok`
and does nothing, while the main window resizes normally.)

Scoping the size rule to the main window — which maps with the title
`Lock Screen — 1Password`, vs the bare `1Password` of the popup — would avoid
applying geometry to a window that rejects it. The `no_screen_share` tag should
of course still cover both.

## 3. Regex nit in the same line

    o.window("^(1[p|P]assword)$", { no_screen_share = true, tag = "+floating-window" })

`[p|P]` is a bracket expression containing a literal `|`, so it also matches
`1|assword`. Presumably `[pP]` was intended. Harmless today, but it reads as an
alternation and isn't one.