WayfireWM / WayfireWM/wcm

Focus Stealing Prevention: Multiple key codes not supported despite plural description

Open
#102 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
52
Forks
12
Avg merge
1h 43m
Merged PRs (30d)
2

Description

Description

The Focus Stealing Prevention configuration option describes its key input field using plural form: "Cancel focus stealing prevention on these keys". This suggests that multiple key codes should be supported, but the current implementation only accepts a single key code.

Expected Behavior

Based on the plural description, it should be possible to specify multiple key codes to cancel focus stealing prevention.

Actual Behavior

Only a single key code works. When attempting to specify multiple keys using various delimiter formats, the configuration is not recognized properly.

Steps to Reproduce

  1. Open Wayfire Configuration Manager
  2. Navigate to Focus Stealing Prevention settings and activate the plugin
  3. Attempt to enter multiple key codes in the key field using different delimiters

Attempted Formats

The following delimiter formats were tested without success:

  • Space-separated: KEY_ENTER KEY_SYSRQ
  • Semicolon-separated: KEY_ENTER;KEY_SYSRQ
  • Comma-separated: KEY_ENTER,KEY_SYSRQ

Working Configuration

Single key codes work as expected, e.g., KEY_SYSRQ

Environment

  • WCM Version: 0.9.0 (current Arch Linux package)
  • Use Case: Screen capturing tool configured in the command section requiring focus stealing prevention bypass

Suggestion

Extend the existing description text "Cancel focus stealing prevention on these keys" to include the required delimiter format, and implement support for multiple key codes if not yet available.

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

Start by tracing how the Focus Stealing Prevention key field is parsed and how its configuration description is defined in Wayfire Configuration Manager. Compare the handling of a single key with the reported space-, semicolon-, and comma-separated forms; done means multiple key codes work with a documented delimiter and the single-key behavior remains intact.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.