-
Notifications
You must be signed in to change notification settings - Fork 129
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
reduced feed list: feed disappears to early [1.10.3] #2
Comments
Hmm... I see the problem. The feed list shows the real state of the feed and the GtkTreeView used for the item list only has a useful trigger for the unread marking when selecting an item. I see no easy way to do it in a better way. I hope this odd behaviour doesn't bother you too much. |
I don't use the reduced feed feature anymore. So… Am 14.12.2013 22:07, schrieb Lars Windolf:
|
This error will not be fixed? It is perfectly okay if the feed disappears in the feed list or even the article list. But it is really unusable that it closes the article view. I made a video so it is easier to see. http://znn.info/files/liferea.ogg It makes it impossible to read the last unread article without changing the view and searching it (because it is marked as read). |
You are right. This needs to be fixed. I didn't get the full effect. Thanks for the video. I'll investigate to see how to fix it easily. |
I tested with 1.10.5 and 1.11 branch and was not able to reproduce the effect so far :-( |
LOL. Forgot that it was fixed in 1.10.4 (see SF ticket #1117 for more info). Please retest! |
Good to know. Will test it and report back. Oh no! Debians liferea package is orphaned. Thanks lwindolf |
I use 1.10.3 on Debian Testing and sync with ttrss.
I use the view where liferea hides feeds with no unread items.
Now, when only one unread item is left and you click it so you can read it… well then liferea immediately hides the feed.
Liferea should wait and hide the feed when the user leaves the feed, so the user has a chance to read the last (unread) item.
The text was updated successfully, but these errors were encountered: