macOS: keep Touch ID and password prompts out of GlazeWM's tiling

Open Beginner friendly
  • Is something wrong?
#63 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
74/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
macos, yaml
Domain
desktop

Research direction

Read macos/glazewm/stowed/.glzr/glazewm/config.yaml and find the existing rule that excludes Control Center windows from tiling. Run glazewm query windows while checking a Touch ID or password prompt to identify the matched process name, then apply the config pattern to those prompts. Done when the prompts open and close without tiled windows moving or resizing; check several prompt sources listed in the issue.

Written by the indexing model from the issue text.

Description

What happens

On macOS, when a system permission prompt appears (a Touch ID prompt, or a
dialog asking for the account password), GlazeWM treats it as a new tiling
window. The tiled windows on the workspace reflow to make room for it, and
reflow again when the prompt closes.

These prompts are short-lived system dialogs. They should appear on top of
the layout without changing it.

Wanted outcome

Touch ID and password prompts leave the tiled layout alone: no windows move
or resize when a prompt opens or closes.

The macOS GlazeWM config is macos/glazewm/stowed/.glzr/glazewm/config.yaml.
It already keeps Control Center's windows out of the layout for the same
reason.

Notes

  • The process names behind these prompts were not confirmed. Likely
    candidates are SecurityAgent (authorization dialogs) and the
    LocalAuthentication UI (coreautha or similar) for Touch ID sheets. Run
    glazewm query windows while a prompt is on screen to see the name GlazeWM
    matches on.
  • Check prompts from several sources, for example sudo with Touch ID, an
    app asking for admin rights, and a System Settings change that needs a
    password.
Dominant language
Lua
Stars
10
Forks
2
Avg merge
4h 53m
Merged PRs (30d)
30

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Gelio/dotfiles

All issues in Gelio/dotfiles

Similar issues

More Lua issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.