Skip to content

Timer behaves strange #23

@monofox

Description

@monofox

Timer running since Start 2025-04-28 20:46:18 local time.
Image
The screenshot was made round about 2025-04-28 21:55:00 local time.

Compare raw output of taskwarrior:

Name          Value
ID            1
Description   Check this task
Status        Pending
Project       TWK
Entered       2025-04-05 21:49:45 (3w)
Waiting until 2025-04-07 00:00:00
Scheduled     2025-04-07 00:00:00
Start         2025-04-28 20:46:18
Due           2025-04-23 00:00:00
Last modified 2025-04-28 20:46:18 (1h)
Virtual tags  ACTIVE MONTH OVERDUE PENDING PRIORITY PROJECT QUARTER READY SCHEDULED UDA UNBLOCKED YEAR
UUID          442fd76d-16bd-4122-ab19-614d7df0902a
Urgency       27.63
Priority      H

    project             1 *    1 =      1
    active              1 *    4 =      4
    scheduled           1 *    5 =      5
    due             0.959 *   12 =   11.5
    age             0.063 *    2 =  0.126
    UDA priority.H      1 *    6 =      6
                                   ------
                                    27.63

I think we can agree, that this is more than one hour, but the timer is something about 1 minute?

I'm not sure, what is exactly the reason. Is it the exceeding of one hour? Is it some quick sleep when the computer was locked for some bio-feedback?

Probably a big improvement would be to store the start time in the html part (maybe as data attribute) and then prober calculate the differences.

Observed in current firefox on Linux as well as Windows.

(While typing, the timer jumped again from 00:02:xx to 00:01:27 ...). Timewarrior had finally 1:15:45 on its clock.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions