Topic notifications are meant to mark read, as a special case. I think with output streaming on it wasn't working right, so that will be fixed.

However, in the general case, it's not expected for notifications to automatically mark as read, as that wasn't implemented as one of the features.

I'll therefore leave this topic open for possible future improvements.

I have output streaming disabled currently on b4 and the problem seems to remain.

So what was the original Composr plan? In other words what would constitute as a "read" notification?

"I have output streaming disabled currently on b4 and the problem seems to remain.
" - you're right. Almost fixed now. Was a block caching issue.

"So what was the original Composr plan? In other words what would constitute as a "read" notification?" - apart from topics, you need to mark them read via the link. I agree with your comments, just it hasn't been done initially and I didn't honestly think of it.

This issue is hard to follow, but as I understand it - we are saying that when you click on a notification to view it (or is it there is a URL attached to it?), it should mark that notification read. Rather than you needing to explicitly click a button to mark notifications read.

Patrick had a look and could no longer find an issue.