One item stays unread in web ui

[rhersel]

IMPORTANT

Read and tick the following checkbox after you have created the issue or place an x inside the brackets ;)

• [ x] I have read the CONTRIBUTING.md and followed the provided tips
• [ x] I accept that the issue will be closed without comment if I do not check here
• [x ] I accept that the issue will be closed without comment if I do not fill out all items in the issue template.

Explain the Problem

There is a regression, that was fixed one year ago. The last feed stays unread. Since version 18.1.0 of the Nextcloud-News-App the issue is back again.

Steps to Reproduce

Explain what you did to encounter the issue

1. Open NC-News-App
2. Scroll through all new feeds
3. The last news stays unread
4. Remedy: get the last feed read by clicking it manually

System Information

• News app version: 18.1.0
• Nextcloud version: 24.0.3
• Cron type: (system cron/python updater/...): System cron
• PHP version: 8.0.21
• Database and version: 10.3.35-MariaDB
• Browser and version: Firefox 103.0
• OS and version: 5.15.57-2-MANJARO

I'm sick and tired of retrieving more details. Sorry, I just want to help in improving the Nextcloud News App. Please come back to me, if the provided details are not sufficient. I will give you all missing information gently.

Paste output here

Contents of Browser Error Console

Read http://ggnome.com/wiki/Using_The_Browser_Error_Console if you are unsure what to put here

Paste output here

[SMillerDev]

This seems to be about the android app?

[Grotax]

I think you mean items? An article of a feed is called an item.

I think this was introduced due to the recently added CSS fix which fixed some other UI bug.

So it was a trade one big for the other.

Additionally with the next Nextcloud version (25) news will become incompatible, even more things won't work then.

I don't know if this can be fixed without reverting the other change.

[rhersel]

Yes, I mean "item". No, I mean the Nextcloud News in a webbrowser (Firefox). I've attached a screenshot which shows the remaining item that will not get marked as read by scrolling. The expected behaviour (as it was before) is, that all items will disappear (marked as read).

[rhyst]

I think this is because the item only get marked as read once the item has scrolled almost beyond the top of the page. In v19 this actually works okay because there's a bunch of blank space at the bottom that means you can scroll past the last item.

@rhersel Is it possible for you to scroll past the last item and if so does it get marked as read?

Either way it should be possible to change the behaviour for the final item so it is marked as read when the bottom of the item clears the bottom of the screen? Maybe that makes more sense?

[DocSniper]

Can confirm the issue and that it has been there for quite a while. The bottom entry is never marked as read, even if you scroll all the way up and the entry has even disappeared completely under the menu bar. My temporary solution to the problem is that I modify the content.css file and add +1px, then the problem is fixed.

File: content.css

141c141
<     height: calc(100vh - 50px);
---
>     height: calc(100vh - 50px + 1px);

[rhyst]

Is this true in v19 of the news app?

For me it is possible to scroll enough that the last item is marked as read, even if it's not ideal UX:

[DocSniper]

Yes, also in version 19.0.0, see screenshots:

[rhyst]

Strangely this just seems to work for me. I have tried in Firefox and Chrome, with compact view and non-compact view, in folders, in the unread articles view, in a single feed. Works every time.

Can you think of anything else to help me reproduce it?

[DocSniper]

Yes, this is all very strange, I don't see any real pattern either, but I'll keep trying. However, I noticed the following:

Tried it with several browsers, the problem seems to exist on most of them, e.g.:

• Firefox on Windows 11
• Ungoogled Chromium on Linux (KDE Plasma + Wayland)
• Firefox on Linux (KDE Plasma + Wayland)
• Falkon on Linux (KDE Plasma + Wayland)

But it works correctly with:

• Firefox on Android (LineageOS)
• Browser on Android (default browser of LineageOS)

Edit: I only used the Android browsers for testing. I usually use the News app on Android.

[DocSniper]

I'm one step closer to the problem. Today I updated Nextcloud from 24 to 25 and the problem seems to be solved (with unmodified NC News 19 content.css). So it's probably the case that NC versions up to 24, depending on the browser, have this error and from NC version 25 on the error no longer occurs. Maybe because of the new look or the themes ?! In any case, I can confirm that the error no longer occurs with NC 25 and NC News 19, at least for me.

[Grotax]

Then I think we can close this, thanks for the fixes and the feedback.