Skip to content
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

notification: Use notification desktop-id to select backend and notify #401

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

3v1n0
Copy link

@3v1n0 3v1n0 commented Nov 2, 2022

This is the continuation of flatpak/xdg-desktop-portal#904

Notifications can provide a specific desktop-id, in such case we should
just use the fdo notifications (to ensure that such info is consumed by
the shell) if the provided ID is not a FDO application ID and pass such
value to it, while when it's a valid application ID we can just use the
gtk backend to have the full experience.

When desktop-id is not provided by the portal, it means it is matching
the application-id, so we consider them the same.

If the gtk name owner value is set it should not be leaked, so use an
auto-pointer for that.
Notifications can provide a specific desktop-id, in such case we should
just use the fdo notifications (to ensure that such info is consumed by
the shell) if the provided ID is not a FDO application ID and pass such
value to it, while when it's a valid application ID we can just use the
gtk backend to have the full experience.

When desktop-id is not provided by the portal, it means it is matching
the application-id, so we consider them the same.
@TingPing

This comment was marked as duplicate.

@smcv smcv marked this pull request as draft November 4, 2022 12:08
@smcv
Copy link
Collaborator

smcv commented Nov 4, 2022

Depends on flatpak/xdg-desktop-portal#904, converted to draft to avoid this getting merged before its required API is stable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants