Skip to content

Inline reply does not send reply text over D-Bus #551

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
maplepy opened this issue May 22, 2025 · 0 comments
Open

Inline reply does not send reply text over D-Bus #551

maplepy opened this issue May 22, 2025 · 0 comments
Labels
bug Something isn't working

Comments

@maplepy
Copy link

maplepy commented May 22, 2025

Summary

When sending a notification with an inline reply action to swaync (SwayNotificationCenter), the notification UI displays the inline reply field correctly. However, when the reply is submitted, only the action key is sent over D-Bus (ActionInvoked signal), and the actual reply text is not sent to the notification sender.

Steps to Reproduce

  1. Send a notification with an inline reply action and input field using the standard org.freedesktop.Notifications interface (e.g., via Python/dbus or notify-send with --hint=string:input).
  2. Enter a reply in the notification pop-up and submit.
  3. Listen for the ActionInvoked signal on D-Bus.

Expected

The ActionInvoked signal or another D-Bus signal should provide the text entered in the inline reply field to the notification sender.

Actual

Only the action key (e.g., 'reply') is sent. The reply text is not accessible to the sender.

Additional Info

  • swaync version: swaync 0.11.0
  • OS: Arch Linux
  • Notification spec: org.freedesktop.Notifications
  • Tested with Python/dbus and notify-send

References

Request:
Please implement support for sending the inline reply text over D-Bus to the notification sender, as per the notification spec, so actionable notifications can handle user replies programmatically.

Thank you!

@ErikReider ErikReider added the bug Something isn't working label May 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants