I have searched the issues of this repo and believe that this is not a duplicate.
OS name and version: Windows 11 Pro 22H2
ActivityWatch version: v0.12.1
Describe the bug
In the activity view, when I use the filter "Count audible browser tab as active", the total active time decrease instead of increasing.
It is as is the audible window time was counted negatively ?
To Reproduce
Go to the activity page
Click on filters
Make sure the checkbox "Count audible browser tab as active" is not selected
remember the activity time for the day
check the box "Count audible browser tab as active"
observe that the activity time has decreased
Expected behavior
With this filter is enabled, the activity time should be greater or equal as when is is not selected (depending on whether you've used audible tabs)
Documentation
Additional context
AW was installed from the windows installer. I have almost not touched the settings. I'm not sure whether I have a browser watcher or not. I I don't the time should not be affected at all anyway.
The text was updated successfully, but these errors were encountered:
Hi there!
As you're new to this repo, please make sure you've used an appropriate issue template and searched for duplicates (it helps us focus on actual development!). We'd also like to suggest that you read our contribution guidelines and our code of conduct.
Thanks a bunch for opening your first issue! 🙏
Describe the bug
In the activity view, when I use the filter "Count audible browser tab as active", the total active time decrease instead of increasing.
It is as is the audible window time was counted negatively ?
To Reproduce
Expected behavior
With this filter is enabled, the activity time should be greater or equal as when is is not selected (depending on whether you've used audible tabs)
Documentation
Additional context
AW was installed from the windows installer. I have almost not touched the settings. I'm not sure whether I have a browser watcher or not. I I don't the time should not be affected at all anyway.
The text was updated successfully, but these errors were encountered: