You are viewing a single comment's thread from:

RE: SteemWorld ~ Weekly Support ~ #31

in #steemworld6 years ago

Hi! Thank you for the awesome Steem app you gave to the community!

I don't know if anybody wrote about this before. I can't find it in the comments. But probably you noticed that browser notifications are fired to whoever visit an account first time after last notifications.

For example if @alice visit steemworld.org/@bob, @alice will see notifications meant to be displayed to @bob about new followers and events on @bob's account. After that @bob will not see his notifications. I've tried in private browser window.

I'm not wining. Your app is cool and gives me lots of insight into Steem stuff. I'm just noticing this issue just in case that you by some chance didn't notice it.

Cheers!

Sort:  

SteemWorld stores the last seen notification per account in the browser cache. For example, when storing the last mention for 'bob', the storage key looks like 'bob.last_mention'.

I could not reproduce the issue on my end. With and without private window it works without any problems...

What I was trying to describe is that I see "bob's" notifications although I'm not "bob". I can record a screencast if that is helpful to you.

I guess that depends on the browser and its implementation of the official Notifications API. When I open 'bob' in one tab and then open 'alice' in a second tab, I see the notifications for both accounts on Firefox (Linux). When I click on a notification for 'bob' while having 'alice' in foreground the browser automatically switches to the correct tab.

When I use only one tab and open a different account with the 'Switch Account' button, the old notifications keep staying there, because there is no way to access/remove them via Notifications API. One thing I could do is to check, if the current tab still contains the original account in the notification's click handler and automatically switch back to the account in this case.

The problem is, I don't know how exactly all the different browsers react in the click handler and if they all correctly focus the source tab. Changing the current logic would be experimental and I have many more important things on my list already, but I will see what I can do in the coming weeks.