You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Add layer-rule instead of mixed with window-rule #259
Maybe it would cool for layer app if added animation like hyprland do. Also maybe contributors can add smooth curve based animation like hyprland, so my rofi can slide from bottom to center instead of popping directly on the screen.
edit:if i'm not busy maybe i can help by opening pr
Splitting them -- yes, definitely. Layer surfaces currently ride on [[window_rules]] by matching their namespace against app_id, and several fields silently apply to only one side (decoration, layer_order, how chrome inherits). A separate [[layer_rules]] table matched on namespace, carrying only the fields that make sense for layers, is the right fix.
Layer animations aren't planned right now. If it happens, it'll be opt-in per layer on the new table (bars and OSDs re-map far too often to animate by default, and a slide needs a direction anyway), so the split has to land first either way. Feel free to open a separate issue for it so this one stays about the rules.
Activity
malbiruk commentedon Sep 5, 2026
Splitting them -- yes, definitely. Layer surfaces currently ride on [[window_rules]] by matching their namespace against app_id, and several fields silently apply to only one side (decoration, layer_order, how chrome inherits). A separate [[layer_rules]] table matched on namespace, carrying only the fields that make sense for layers, is the right fix.
Layer animations aren't planned right now. If it happens, it'll be opt-in per layer on the new table (bars and OSDs re-map far too often to animate by default, and a slide needs a direction anyway), so the split has to land first either way. Feel free to open a separate issue for it so this one stays about the rules.