Bug 224019

Summary:	reading time: is counted when akregator is not active
Product:	[Applications] akregator	Reporter:	Maciej Pilichowski <bluedzins>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	CONFIRMED ---
Severity:	wishlist	CC:	osterfeld
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	openSUSE
OS:	Unspecified
Latest Commit:		Version Fixed In:

Description Maciej Pilichowski 2010-01-24 12:24:31 UTC

Version:            (using KDE 4.3.3)
Installed from:    SuSE RPMs

ver. 4.3.90

Example:
1. A. is in the systray
2. it has 1 message unread
3. I click on its icon to "open" it
4. I click on the message and _immediately_ I click close to hide it
5. obviously I didn't read the message
6. few seconds later A. marks it as read

Comment 1 Frank Osterfeld 2010-02-06 20:35:34 UTC

That's inaccuracy one has to live with, I think. Define what qualifies as definitely not read" then.
closed? minimized? In the background? preview widget partly covered by another window? I could have Akregator on a separate screen on not have read the article, even if it was perfectly visible all the time.
The purpose of the delayed marked as read function is to prevent articles from being marked as read when navigating through the article list quickly, it doesn't try to be more accurate than that.

Comment 2 Maciej Pilichowski 2010-02-06 21:10:34 UTC

> That's inaccuracy one has to live with, I think.

When you have your leg broken you go to a doctor or "you have to live with it"? If you think that broken behaviour is OK, at least please give a reason.

> Define what qualifies as definitely not read" then.

Definitely: 
a) minimized window
b) no window 

This is as solid as math proof. Other aspects (like window in the background) are subjective and belongs to general usability, but those two -- no. They are solid.

> The purpose of the delayed marked as read function

No complains here. I am saying it is totally odd that program claims I read something in situation I am not physically able read anything at all (each user set his/her capabilities of reading as a timeout, if somebody sets timeout to 0.1 ms, well, no blame to Akregator for sure, but it is not the case here).

Comment 3 Justin Zobel 2021-03-09 04:11:57 UTC

Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.