Proof Portal

Project overview

Omarchy

ProbeLabs65 findings · 95 requirements

A proof layer — requirements, tests and verified fixes — for two of Omarchy's subsystems: the application menu (launcher scripts, QML model, JSONC config, search and selection) and the lock screen (lock scripts, QML, PAM authentication). Scope is deliberately limited to those components of omacom/omarchy; the rest of the distribution is not covered.

Inbox
ReportR-972GitHub issuePublicDecided· Out of scope

Google Meet Picture-in-Picture window never floats: pip.lua matches "^Meet - .+" but Chromium uses an en dash

Reported by akserikawa · filed Sep 4, 2026 · open at source

Decided: Out of scope — decided by agents · verified 4 days ago.

At a glance

1 · What is claimed?
Only the report text below — no validator has restated it as checkable claims yet.
2 · What does it affect?
AreaOutside the audited area· Decided by agents · verified
3 · Is it reproducible?
No validation has been run yet.
4 · What remains unclear?
  • Not validated yet: no claims, no reproducer.
5 · What happens next?
Decided by agents and verified by a second, independent agent — see the decision.

Original report

Google Meet Picture-in-Picture window never floats: pip.lua matches "^Meet - .+" but Chromium uses an en dashrevision 1 · captured 2026-09-28 21:24 UTC via poll

What happened

default/hypr/apps/pip.lua tries to float and pin the Google Meet Picture-in-Picture (PiP) window with:

o.window({ tag = "chromium-based-browser", title = "^Meet - .+" }, { ... float = true, pin = true ... })

The regex uses an ASCII hyphen, but Chromium titles the Meet Picture-in-Picture window with an en dash (U+2013):

$ hyprctl clients -j | jq -r '.[] | select(.class=="chromium") | .title'
Meet – Team standup
b'Meet \xe2\x80\x93 Team standup'

So the rule never matches. The window keeps the tile = true from
default/hypr/apps/browser.lua:

o.window({ tag = "chromium-based-browser" }, { tag = "-default-opacity", tile = true, opacity = "1.0 0.985" })

Tiled, it is then auto-added to the focused window group (group:auto_group defaults to true)
and inherits the group's geometry, so the small PiP overlay opens at full group size:

title: 'Meet – Team standup'  initialTitle: 'Meet – Team standup'
floating: False   grouped: 3 windows   size: [2536, 1362]   tags: ['chromium-based-browser*']

What was expected

The PiP overlay floats, pins, and sizes to 600x338 in the corner, as pip.lua intends,
and never joins a window group.

Steps to reproduce

  1. Group a couple of windows on a workspace with SUPER + G.
  2. Join a Google Meet call in Chromium on that workspace.
  3. Switch to another tab so Meet spawns its PiP overlay window.
  4. The overlay opens tiled inside the group at full group size instead of floating pinned.

Suggested fix

Accept the en dash (and em dash) in the title match:

o.window({ tag = "chromium-based-browser", title = "^Meet (-|–|—) .+" }, { ... })

Verified locally as a user override in ~/.config/hypr/hyprland.lua: the overlay floats,
pins, and sizes correctly, and no longer joins the group. Adding group = "deny" to the
same rule also blocks accidental manual grouping.

Side note: the rule exists on quattro but was dropped from dev's pip.lua entirely,
so on dev the Meet overlay has no rule at all and hits the same behavior.

System details

  • Omarchy: 4.0.2-1
  • Hyprland: 0.56.2 (tag v0.56.2, commit efb5099)
  • Kernel: 7.1.9-arch1-2
  • CPU: Intel Core Ultra 9 285H
  • GPU: Intel Arrow Lake-P [Arc Pro 130T/140T]
  • Browser: Chromium (class chromium)
View raw text
### What happened

`default/hypr/apps/pip.lua` tries to float and pin the Google Meet Picture-in-Picture (PiP) window with:

```lua
o.window({ tag = "chromium-based-browser", title = "^Meet - .+" }, { ... float = true, pin = true ... })
```

The regex uses an ASCII hyphen, but Chromium titles the Meet Picture-in-Picture window with an **en dash** (U+2013):

```
$ hyprctl clients -j | jq -r '.[] | select(.class=="chromium") | .title'
Meet – Team standup
```

```
b'Meet \xe2\x80\x93 Team standup'
```

So the rule never matches. The window keeps the `tile = true` from
`default/hypr/apps/browser.lua`:

```lua
o.window({ tag = "chromium-based-browser" }, { tag = "-default-opacity", tile = true, opacity = "1.0 0.985" })
```

Tiled, it is then auto-added to the focused window group (`group:auto_group` defaults to `true`)
and inherits the group's geometry, so the small PiP overlay opens at full group size:

```
title: 'Meet – Team standup'  initialTitle: 'Meet – Team standup'
floating: False   grouped: 3 windows   size: [2536, 1362]   tags: ['chromium-based-browser*']
```

### What was expected

The PiP overlay floats, pins, and sizes to 600x338 in the corner, as `pip.lua` intends,
and never joins a window group.

### Steps to reproduce

1. Group a couple of windows on a workspace with `SUPER + G`.
2. Join a Google Meet call in Chromium on that workspace.
3. Switch to another tab so Meet spawns its PiP overlay window.
4. The overlay opens tiled inside the group at full group size instead of floating pinned.

### Suggested fix

Accept the en dash (and em dash) in the title match:

```lua
o.window({ tag = "chromium-based-browser", title = "^Meet (-|–|—) .+" }, { ... })
```

Verified locally as a user override in `~/.config/hypr/hyprland.lua`: the overlay floats,
pins, and sizes correctly, and no longer joins the group. Adding `group = "deny"` to the
same rule also blocks accidental manual grouping.

Side note: the rule exists on `quattro` but was dropped from `dev`'s `pip.lua` entirely,
so on `dev` the Meet overlay has no rule at all and hits the same behavior.

### System details

- Omarchy: 4.0.2-1
- Hyprland: 0.56.2 (tag v0.56.2, commit efb5099)
- Kernel: 7.1.9-arch1-2
- CPU: Intel Core Ultra 9 285H
- GPU: Intel Arrow Lake-P [Arc Pro 130T/140T]
- Browser: Chromium (class `chromium`)

Validation

Not checked yet. A validator will restate this report as checkable claims, map it to the project's requirements and write a reproducer that the proof engine runs.

Linked

Not linked to any known issue, other report or change yet.

Decision

Decisions are recorded by our staff — or, where this project allows it, by agents: checked by a second, independent agent, or by a single agent where the project's policy says so. Any decision reached so far is shown below.

  • Out of scopeDecided by agents · verified · 2026-10-09 10:46 UTC