@mihael said:
can't the "load" be included in the notification bubble as well? And then the UI adds the possibility for the user to interact with the bubble by tapping on it.
I have looked at the spec for push notifications. Not the http notifications via the ubports push server, the notifications via d-bus, the so-called "low-level API", the 'postal message':
[image: 1780073132741-helperoutput.png]
here is an exemple use from Dekko source code:
QJsonObject NotificationWatcher::buildSummaryMessage(const QString &msg) {
QString appDir = QCoreApplication::applicationDirPath();
appDir.replace(QRegExp("dekko2.dekkoproject/.*"), "dekko2.dekkoproject/current/");
QString icon = QString("file://").append(appDir).append("dekko.png");
QJsonObject c;
c["summary"] = msg;
c["popup"] = true;
c["persist"] = true;
c["icon"] = icon;
QJsonArray actions = QJsonArray();
QString actionUri = QStringLiteral("appid://dekko2.dekkoproject/dekko/current-user-version");
actions.append(actionUri);
c["actions"] = actions;
QJsonObject notification;
notification["card"] = c;
notification["sound"] = true;
notification["vibrate"] = vibrate();
QJsonObject message;
message["notification"] = notification;
return message;
}
what is important is that Dekko does everything 'right' to allow for the system to activate it when clicking (pressing) the bubble notification. There is nothing that Dekko is purposely NOT doing to disable this capability that is said to be possible in plain english in the doco:
If you add a URL, then bubble notifications are clickable and launch that URL.
so it can be considered like a bug, yes. I'm changing my point of view here. Per the doc, it was designed to work like you want it to work, but obviously it don't (I checked again with Dekko).
I guess that it has never worked like that though.
For apps that are using the high level Api, I don't know if it's even possible to pass an activation URI so it's possible that this capability was not really wanted as it seemed just not doable.
