Notifications not cancelling.

Russ Freeman said

Unfocussed Mike said

Russ Freeman said

I can't reproduce it, and there is no "reduce notifications by one" functionality since ALL notifications are cleared when they are displayed.

Clicking a notification, for example, a comment was left on an image, does not clear 1 notification or change the "read" status of a single notification since such functionality simply does not exist.

A video of this behaviour would certainly clarify what is going on and reduce ambiguities.

I have seen this on and off --  hasn't happened today but it has happened in different browsers. Difficult to catch it in a video on the iPad but as I am out for a chunk of the day and notifications might start to build up I can test it in Mac Safari.

Most notably it happened when a model I follow uploaded ten different photos before I saw the notifications for any of them. I really did have to click each one -- open the page and the number had gone down by only one.

When you say you clicked each one, what does that mean? 

Clicking on the "thing" navigates to whatever the thing is (image, group post) but there is no functionality when viewing an image or a group post to reduce the notification by 1. It simply doesn't exist. This is why I am confused by this report and would like a video of it.

I mean clicked the actual notification body -- in this case one of the images in the "uploaded X images" bit.

You navigate to the thing: the number was only one less.

I will try to get a video if it happens again.

So as there's no such mechanism then the challenge surely is working out why the server tells the client there is a number one less than last time. Duplicate notifications? Strange time synchronisation issues? (DB and app server out of clock sync? I have seen this happen in my own apps)

Edited by Unfocussed Mike

Unfocussed Mike said

Russ Freeman said

Unfocussed Mike said

Russ Freeman said

I can't reproduce it, and there is no "reduce notifications by one" functionality since ALL notifications are cleared when they are displayed.

Clicking a notification, for example, a comment was left on an image, does not clear 1 notification or change the "read" status of a single notification since such functionality simply does not exist.

A video of this behaviour would certainly clarify what is going on and reduce ambiguities.

I have seen this on and off --  hasn't happened today but it has happened in different browsers. Difficult to catch it in a video on the iPad but as I am out for a chunk of the day and notifications might start to build up I can test it in Mac Safari.

Most notably it happened when a model I follow uploaded ten different photos before I saw the notifications for any of them. I really did have to click each one -- open the page and the number had gone down by only one.

When you say you clicked each one, what does that mean? 

Clicking on the "thing" navigates to whatever the thing is (image, group post) but there is no functionality when viewing an image or a group post to reduce the notification by 1. It simply doesn't exist. This is why I am confused by this report and would like a video of it.

I mean clicked the actual notification body -- in this case one of the images in the "uploaded X images" bit.

You navigate to the thing: the number was only one less.

I will try to get a video if it happens again.

So as there's no such mechanism then the challenge surely is working out why the server tells the client there is a number one less than last time. Duplicate notifications? Strange time synchronisation issues? (DB and app server out of clock sync? I have seen this happen in my own apps)

When you click on the flashing number your web client requests the notifications and so the server gathers them, clears the unread status of them all using a trivial SQL update, and then sends them to the client.

There are exactly zero other ways the notifications are cleared.

A video of it would be enlightening.

Russ Freeman said

When you click on the flashing number your web client requests the notifications and so the server gathers them, clears the unread status of them all using a trivial SQL update, and then sends them to the client.

There are exactly zero other ways the notifications are cleared.

A video of it would be enlightening.

This happened on my f11 studio account yesterday.

Isn't happening on this account.

Thinking back, I recalled that it had been reported so assumed it would be fixed in due course and didn't take careful note, but I'm not sure that the count decremented even after clicking one of the alerts.  I think it did, by 1.

"Flashing number" I click on the speech bubble, I think?

MidgePhoto said

Russ Freeman said

When you click on the flashing number your web client requests the notifications and so the server gathers them, clears the unread status of them all using a trivial SQL update, and then sends them to the client.

There are exactly zero other ways the notifications are cleared.

A video of it would be enlightening.

This happened on my f11 studio account yesterday.

Isn't happening on this account.

Thinking back, I recalled that it had been reported so assumed it would be fixed in due course and didn't take careful note, but I'm not sure that the count decremented even after clicking one of the alerts.  I think it did, by 1.

"Flashing number" I click on the speech bubble, I think?

Yes, with the red box that has a white number inside it.

It flashes several times when the web page is first displayed.

Russ Freeman said

hyperphoto said

Happening on Win10 Chrome & Android Chrome - When you click the 'cancel' button the number on the little red sign reduces by 1.

That is perfect, can you please share a video of that happening?

Don't want to speak to soon but everything appears to be working ok for me now - didn't even have to click the 'cancel' button for the red sign to disappear once the notification had been read :)

Russ Freeman Thought it was ok - but still appears to be doing it - took a quick vid to show ( link below ) :)

hyperphoto that is great, thank you.

What happens if you click it again, does the popup show yellow notifications or all just white?

Also, if you refresh the page does it the red thing go away or remain?

Edited by Russ Freeman

Russ Freeman said

hyperphoto that is great, thank you.

What happens if you click it again, does the popup show yellow notifications or all just white?

No worries - Ah, I've run out of notifications at the moment but will let you know what happens when I get some more :)

Russ Freeman said

hyperphoto that is great, thank you.

What happens if you click it again, does the popup show yellow notifications or all just white?

Also, if you refresh the page does it the red thing go away or remain?

Edited by Russ Freeman

This is what I experienced. The red thingy (that is now the proper technical term for this feature!) remained when I refreshed, but that was on the iPad and *wavey-hands-about-mobile-browser-caching*

Unfocussed Mike said

Russ Freeman said

hyperphoto that is great, thank you.

What happens if you click it again, does the popup show yellow notifications or all just white?

Also, if you refresh the page does it the red thing go away or remain?

Edited by Russ Freeman

This is what I experienced. The red thingy (that is now the proper technical term for this feature!) remained when I refreshed, but that was on the iPad and *wavey-hands-about-mobile-browser-caching*

It's a single XHR request to get AND clear the notifications. Where do you imagine mobile browser caching might find into that single request to the server?

Russ Freeman said

Unfocussed Mike said

Russ Freeman said

hyperphoto that is great, thank you.

What happens if you click it again, does the popup show yellow notifications or all just white?

Also, if you refresh the page does it the red thing go away or remain?

Edited by Russ Freeman

This is what I experienced. The red thingy (that is now the proper technical term for this feature!) remained when I refreshed, but that was on the iPad and *wavey-hands-about-mobile-browser-caching*

It's a single XHR request to get AND clear the notifications. Where do you imagine mobile browser caching might find into that single request to the server?

I don't know but I have long learned not to expect mobile devices to do the right thing! One of my few outstanding "never fixed it, no effing idea" work problems is a mobile browser issue.

Unfocussed Mike said

Russ Freeman said

Unfocussed Mike said

Russ Freeman said

hyperphoto that is great, thank you.

What happens if you click it again, does the popup show yellow notifications or all just white?

Also, if you refresh the page does it the red thing go away or remain?

Edited by Russ Freeman

This is what I experienced. The red thingy (that is now the proper technical term for this feature!) remained when I refreshed, but that was on the iPad and *wavey-hands-about-mobile-browser-caching*

It's a single XHR request to get AND clear the notifications. Where do you imagine mobile browser caching might find into that single request to the server?

I don't know but I have long learned not to expect mobile devices to do the right thing! One of my few outstanding "never fixed it, no effing idea" work problems is a mobile browser issue.

Since the reports suggest devices other than mobiles logically it cannot be a mobile browsing caching issue.

Russ Freeman said

hyperphoto that is great, thank you.

What happens if you click it again, does the popup show yellow notifications or all just white?

Also, if you refresh the page does it the red thing go away or remain?

Edited by Russ Freeman

Ok, got some more notifications in. This is how it went down:

Red thingy shows a '3'

click red thingy --------------> shows the 3 notifications in yellow

click cancel

Red thingy shows a '2'

click red thingy --------------> shows the 2 notifications in yellow

click cancel

Red thingy shows a '1'

click red thingy --------------> shows the 1 notification in yellow

click cancel

Red thingy disappears

Refreshing the page at any point during this doesn't appear to do anything - red thing remains.

Hope this helps :)

Edited by hyperphoto

That's a great clue, thank you.

hyperphoto - please can you share a video of the behaviour you describe above.