feat: notification interactions & lock screen privacy - #11
Open
TraNzeM wants to merge 3 commits into
Open
Conversation
- 弹出通知: hover 展开操作按钮、inline reply、点击跳转应用、urgency 色条 - 通知中心: 点击通知跳转应用、分组展开逻辑 - 锁屏通知隐私: 显示内容/隐藏内容/全部隐藏 (Keystone 设置) - i18n: en_US/zh_CN/zh_TW 三语言
TraNzeM
force-pushed
the
feat/notification-interactions-and-lock-privacy
branch
from
August 27, 2026 10:40
501d8dd to
4ea5530
Compare
Клик по телу уведомления теперь активирует приложение даже когда у уведомления нет действий (default action) или оно загружено из истории без живого серверного объекта. desktopEntry персистится в JSON и используется как fallback через gtk-launch (freedesktop).
Clicking a notification body now resolves the target app through DesktopEntries.heuristicLookup(appName) when the server notification has no actions and desktopEntry is empty (Quickshell only fills desktopEntry from an explicit DBus hint 'desktop-entry', which most apps omit). Previously the click just dismissed the notification whenever desktopEntry was unset; appName (e.g. org.telegram.desktop) now maps to the real .desktop id so gtk-launch can bring the app to focus.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Notification UX improvements and lock screen privacy, following modern practices (GNOME 46+, KDE Plasma, Windows 11, Android).
1. Popup interactions (Keystone NotificationContent)
HoverHandler(nested MouseAreas caused collapse/expand loop)2. Notification center click-to-activate
3. Lock screen notification privacy (Android-style)
Three modes in Keystone settings (
通知隐私/ Notification privacy):show— show full content (default)hide-content— app icon/name/time visible, text hidden withvisibility_offplaceholderhide-all— notification card hidden entirelyPersisted in
ui-preferences.json(lockScreenNotificationPrivacy).4. i18n — all three locales
New strings added to
en_US,zh_CN,zh_TW(.ts + rebuilt .qm, 1403 translations per locale, 0 unfinished).Files
Services/NotificationManager.qml— inline-reply capability,invokeDefaultAction,sendInlineReply, timeout resumeServices/UiPreferences.qml—lockScreenNotificationPrivacy+ persistenceModules/Keystone/NotificationContent/NotificationContent.qml— hover actions, reply, urgency stripModules/Keystone/Styles/Shared/KeystoneSurface.qml— dynamic popup height, keyboard focus for replyModules/Sidebars/Left/notifications/NotificationGroup.qml,NotificationItem.qml— click-to-activateModules/Lock/Cards/NotificationCard.qml— privacy modesModules/ControlCenter/KeystonePage.qml— privacy setting UIi18n/clavis_{en_US,zh_CN,zh_TW}.ts— translationsQuality
git diff --check,lint-qml.shpassed, CTest 10/10, CMake build cleanformat-qml.sh --checkonNotificationManager.qmlfails on the current qmlformat (1.0, qt6-declarative 6.11.2) due topragma ComponentBehavior: Bound— pre-existing issue, also fails on the file from upstream HEAD