click on notification bubble

CiberSheep

@mihael that's the behavior by design.
Notification bubbles turns the screen on (you can swipe them away).
Notification in the Notifications indicator are clickable, they should open the app or addition options (like the quick answer from SMS app).

The only notification bubble that doesn't follow that rule (and others) is the one from Dialer

gpatel-fr

@mihael

if you mean by 'address the issue' actually create an issue for each of the apps you want changed as you like, I'd say with a high degree of probability that your issues will be closed or ignored.

If you meab 'create a MR', then it could be discussed but likely rejected for the same reason.

Notifications are meant to be temporary. If they become an UI, the notifications will almost inevitably be longer, or even become permanent. So they will stack. If can become a hot mess and even hinder the phone notifications for incoming calls.

This could be adressed by making the feature optional but you'll see that it implies some maintenance work for the project owner, even if the MR is fully complete and functional.

mihael

I mean, it would be nice just to click on the first thing that wakes the screen up and take you to the app, wouldn't it? - and that first thing is the bubble...

gpatel-fr

@mihael

Well, I have tried to make clear that there are several aspects to this feature and not all of them are pointing in the same direction; what is obvious to you may be more ambiguous for others.

I have always hated one feature of the most used operating system of the planet and as far as I know I have never seen another people expressing the same disgust so I'm probably the only one. It' may be possible that you are the only people in the world that would feel strongly about that even if UT had 6 billions users.

mihael

@gpatel-fr Yes, I think talking about this in a forum is healthy and helps me (maybe others too) understand what others are thinking because it may not in the end be something that is desired...

I guess my first intention in asking the initial question was to see if this is an expected behaviour or it was rather supposed to work and it doesn't anymore.

So I understand that it was never meant (yet) to work this way - to click on the bubble and open the app that the bubble reffers to.

Then, I guess, I tried to ask if this is something that would be desired.

Then, I guess again, in case that would be a good idea, it would be the question if that is something that can be done.

projectmoon

I agree with this. Swiping the notification makes it disappear into the list. Tapping the notification should just execute the notification handler, like tapping it from the notification list does.

mihael

@projectmoon said:

Tapping the notification should just execute the notification handler

You mean "tapping the notification bubble"?

projectmoon

@mihael yes, tapping the floating one that appears when the notification appears. It doesn't make sense to me to have the tap dismiss the notification into the notification bar, when you can do that with a swipe.

brenno.almeida

Its definitely a Lomiri UI inconsistency, not an app issue. From apps perspective, there's no way to tweak this behavior. And there's no difference between an app using dbus or the http apis to send notifications, they end up flowing over the same path in your device.

gpatel-fr

@brenno.almeida said:

From apps perspective, there's no way to tweak this behavior.

not sure what you are meaning by 'this behavior' and 'tweaking'.

What I understand is there would be no way to display a time out notification and detect if the user has pressed the notification before it closes by itself.

If this is what you mean, this example shows how it can be done..

Granted, don't know if this can work from an unconfined app. This caveat was not part of the discussion