From 794a455e4499bf2124dbb22e948c588500d356a2 Mon Sep 17 00:00:00 2001
From: "Birkir A. Barkarson" <birkirb@stoicviking.net>
Date: Fri, 12 Sep 2025 11:44:03 +0200
Subject: [PATCH] Warning on "initial" matching

Note that specifically trying to match on initialClass or initialTitle, doesn't seem to work. (which is what matching on title and class does anyway)
---
 content/Configuring/Window-Rules.md | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/content/Configuring/Window-Rules.md b/content/Configuring/Window-Rules.md
index 6f19bd48f..361502df6 100644
--- a/content/Configuring/Window-Rules.md
+++ b/content/Configuring/Window-Rules.md
@@ -142,6 +142,18 @@ It is not possible to `float` (or any other static rule) a window based on a cha
 | content \[none\|photo\|video\|game\] | Sets content type. |
 | noclosefor \[ms\] | Makes the window uncloseable with the `killactive` dispatcher for a given amount of ms on open. |
 
+{{< callout type=warning >}}
+
+When using tags with static rules, ensure tags are assigned using `class:` or `title:` matching rather than `initialClass:` or `initialTitle:`. Static rules like `workspace` may be processed before tags assigned via initial properties are available, causing the rule to be ignored.
+
+**Example of problematic configuration:**
+```ini
+windowrule = workspace 3, tag:myapp
+windowrule = tag +myapp, initialClass:^myapp.*  # May not work with workspace rule
+```
+
+{{< /callout >}}
+
 ### Dynamic rules
 
 Dynamic rules are re-evaluated every time a property changes.