On 2017-03-13 18:52, nospam wrote:
In article , Alan Browne
wrote:


It's not necessarily a bug (or at least not a serious bug) for an app to
not update its own time reference - see my other post.

it is a bug, although minor and easily resolved.

What part of 'at least not a serious bug' flew so high over your head
that you had absolutely to rebutt that.

you said 'it's not necessarily a bug'. that is incorrect. it *is* a bug.

Then I qualified it rather than edit it out which was an option to pass
the nospam obsessive filter. But I left it. Like a conversation.

This is why you're so popular nospam. You can't relate to a posting as
if it's polite conversation. You rubutt the slightest inconsistency as
if it matters when it doesn't. Learn to grow your grey zone.


whenever an app displays incorrect data, regardless of what that data
is, it's a bug.

we do agree that the bug is minor, so no rebuttal there.

It's not a serious bug nor one that occurs often.

actually, it's fairly common.

The bug in question only occurs 2 times per year in the app in question.

--
"If war is God's way of teaching Americans geography, then
recession is His way of teaching everyone a little economics."
..Raj Patel, The Value of Nothing.